Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp1139084ybi; Fri, 21 Jun 2019 14:46:02 -0700 (PDT) X-Google-Smtp-Source: APXvYqyjsNohjEmoPYIP6DQiRb/xk0kIraM+/RQytOHMsitfKtqG3E7C7m5qJgWge7kw/OKnqhYr X-Received: by 2002:a63:4105:: with SMTP id o5mr21150986pga.308.1561153562396; Fri, 21 Jun 2019 14:46:02 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1561153562; cv=none; d=google.com; s=arc-20160816; b=ivJ7AkScduo2EfXvZaOTvDdQIvnZd4Ai2lQaW4JHthTY+mc2XcWKl5QxIUIpOIbVg/ ESkeNWsS9odGT2PmV+zZDfM4YP1APQxpFWNdvI4Ge5DNTAVOY7t3TTvq9BgN4TG+ArWR WSdfnwCDJjSfs1iQYePtrpskaGldbURIgsGeESYSkVDJSnhDNbluKx7q3Iummjm8nNee f05N2ztD0d5AAUIegSiAk0jVGkPsgd6MtBJVwTBwV8mrUcmDSTjk5F+LogU467l6dbfG cCMUcLEnjsfZXOTEd1o292/oSPEI7y7/HtKUV749/ArSGUVRhcnTGBKrofnCgXUT1D7l B3+w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature; bh=tuPPC6lpYujCl3/C4gjdhayCmhw5/kYOpTCP4JitViI=; b=xxgkEdQ6M4C8MUbwm+H9onR/HLw49UTnSCgVWT98DW27xeOuqOC9+TWu1P2BTgbVwm Zpv/NzbX02MSt2Lsy+A6rISF1SJDLLNl6mxIvZcRFFZkOtZyTPaIkbDLkINXk2eiQXaC Y4jlauovWVuU3boXZHcPzP7WGGJ9s91tQWTCFukDnh5XZ1fANYH0wAfigRb8f9bwppe8 1FpDHya6EhMcxYNry8rKwIACHzs2zEZJ1bOtmRmlUX21u2my2Woknbca4QQb2eysYCQI 7MEq0ObYnV4vHUGx5NUp0fqJBCKl6U3BXeRB8SeblDcPVNlm2Az0GpsN/mqXytabSJ/v hImw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@valvesoftware.com header.s=mc20150811 header.b=BYGJMhpp; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 2si3630292ple.275.2019.06.21.14.45.46; Fri, 21 Jun 2019 14:46:02 -0700 (PDT) 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; Authentication-Results: mx.google.com; dkim=pass header.i=@valvesoftware.com header.s=mc20150811 header.b=BYGJMhpp; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726066AbfFUVpf (ORCPT + 99 others); Fri, 21 Jun 2019 17:45:35 -0400 Received: from us-smtp-delivery-172.mimecast.com ([216.205.24.172]:24733 "EHLO us-smtp-delivery-172.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725985AbfFUVpf (ORCPT ); Fri, 21 Jun 2019 17:45:35 -0400 X-Greylist: delayed 972 seconds by postgrey-1.27 at vger.kernel.org; Fri, 21 Jun 2019 17:45:35 EDT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=valvesoftware.com; s=mc20150811; t=1561153534; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=tuPPC6lpYujCl3/C4gjdhayCmhw5/kYOpTCP4JitViI=; b=BYGJMhpp1VxhuumvghGFn9VR7b6a1f/PWnJAkP6dywcywZvkV1BbMqdQdaT3497Cxc0zuJ JYchvYoqd6Ckw4biZgiuSMvXIMmRogR3mKT/kxWLZ+r4s0/GAg+/II2HL3zrxCDwKdAQfB 6sQJigkuLnYtvWoCAgsTb2+Qvmc6HR4= Received: from smtp01.valvesoftware.com (smtp01.valvesoftware.com [208.64.203.181]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-293-sOngGh1eMlmn39ClzDlAwA-1; Fri, 21 Jun 2019 17:45:33 -0400 Received: from [172.16.1.107] (helo=antispam.valve.org) by smtp01.valvesoftware.com with esmtp (Exim 4.86_2) (envelope-from ) id 1heRYG-000AIb-78 for linux-kernel@vger.kernel.org; Fri, 21 Jun 2019 14:58:32 -0700 Received: from antispam.valve.org (127.0.0.1) id h1l7vo0171su for ; Fri, 21 Jun 2019 14:45:32 -0700 (envelope-from ) Received: from mail1.valvemail.org ([172.16.144.22]) by antispam.valve.org ([172.16.1.107]) (SonicWALL 9.0.5.2081 ) with ESMTP id o201906212145320014067-5; Fri, 21 Jun 2019 14:45:32 -0700 Received: from [172.18.41.51] (172.18.41.51) by mail1.valvemail.org (172.16.144.22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1415.2; Fri, 21 Jun 2019 14:44:27 -0700 Subject: Re: Steam is broken on new kernels To: Greg Kroah-Hartman CC: , lkml , References: <20190621214139.GA31034@kroah.com> From: "Pierre-Loup A. Griffais" Message-ID: <6033e333-137b-9016-bfdc-62ed747835ef@valvesoftware.com> Date: Fri, 21 Jun 2019 14:43:54 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: <20190621214139.GA31034@kroah.com> Content-Language: en-US X-ClientProxiedBy: mail1.valvemail.org (172.16.144.22) To mail1.valvemail.org (172.16.144.22) X-EXCLAIMER-MD-CONFIG: fe5cb8ea-1338-4c54-81e0-ad323678e037 X-Mlf-CnxnMgmt-Allow: 172.16.144.22 X-Mlf-Version: 9.0.5.2081 X-Mlf-License: BSVKCAP__ X-Mlf-UniqueId: o201906212145320014067 X-MC-Unique: sOngGh1eMlmn39ClzDlAwA-1 X-Mimecast-Spam-Score: 0 Content-Type: text/plain; charset=WINDOWS-1252; format=flowed Content-Transfer-Encoding: quoted-printable Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 6/21/19 2:41 PM, Greg Kroah-Hartman wrote: > On Fri, Jun 21, 2019 at 02:27:41PM -0700, Pierre-Loup A. Griffais wrote: >> 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= _connect_on_kernels_newer_than/ >> >> https://www.phoronix.com/scan.php?page=3Dnews_item&px=3DSteam-Networking= -Kernel-Woes >> >> I don't really understand that distributions that claim to be desktop >> products would have fast-tracked a server-oriented fix to all their user= s >> without testing one of the primary desktop usecases, but that's another >> thing to figure out later. >> >=20 > What specific commit caused the breakage? Unclear as of yet, we're starting that process on our end just now. Not=20 sure if a user has already performed a bisect and shared his findings in=20 one of the links below, but we'll be scouring these and doing our own=20 testing as next steps. >=20