Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
To:     Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        <edumazet@google.com>, lkml <linux-kernel@vger.kernel.org>
From:   "Pierre-Loup A. Griffais" <pgriffais@valvesoftware.com>
Subject: Steam is broken on new kernels
CC:     <torvalds@linux-foundation.org>
Message-ID: <a624ec85-ea21-c72e-f997-06273d9b9f9e@valvesoftware.com>
Date:   Fri, 21 Jun 2019 14:27:41 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101
 Thunderbird/60.0
MIME-Version: 1.0
Content-Language: en-US
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

This seems to have broken us:

https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.1.11

Here's some affected users:

https://github.com/ValveSoftware/steam-for-linux/issues/6326

https://www.reddit.com/r/linux_gaming/comments/c37lmh/psa_steam_does_not_co=
nnect_on_kernels_newer_than/

https://www.phoronix.com/scan.php?page=3Dnews_item&px=3DSteam-Networking-Ke=
rnel-Woes

I don't really understand that distributions that claim to be desktop=20
products would have fast-tracked a server-oriented fix to all their=20
users without testing one of the primary desktop usecases, but that's=20
another thing to figure out later.