Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp1221992ybi; Fri, 21 Jun 2019 16:44:00 -0700 (PDT) X-Google-Smtp-Source: APXvYqyRivRCnaTVsnJwiE8VX1k3Riu6w7fOSDDJwaTaM3G58baFbJcNlaA41N3uEJyMJwRBde3J X-Received: by 2002:a63:db05:: with SMTP id e5mr20915309pgg.121.1561160639990; Fri, 21 Jun 2019 16:43:59 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1561160639; cv=none; d=google.com; s=arc-20160816; b=JGIlrBamRDN7ocoY+5zWlpx/jckMYlSN2e2JnmH/vu443ZcsybkT0GpPnthpx7jw/a zEWXuY2kvdJUQZOH8e6CCwEjGcq2KGLe8aCQiHY8mebyVjsEjP/Sd6Pzc7N0bDfGvB3J 8ITuKuStkMupqqkCE5monuUpEykmKkINkJaIJ7TnERjkpZvL/ZpsfKoMrGYinFfmm0M4 mQFiOgNw4hTdJu/2Z/ZMobdnBXv/PuJ0uwo0dBesetaRF4DVhG0NqHBkVTwCkr742sDh chB1tvRhZO0OXD+pXybXpYHtCrIeZjS/OFbN2Wts65m5DN51pYOMdmJYzhxx1pwFWOjf pgLw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=tmluSxzqhi5CcpOX2qxUxSbj+sNH9VpLrhtNj2D7dDA=; b=0gdVPhbactykNIcl3+dTByjKQYryTVHW1BARTmn5FKQrvwFW+NqC63x38GLnNwhEuR jS032n+6/Pi6WWQ1UYloaMhH2QrHRHGgvNeOvWYsL0gnuUH5u1FDBJG/LkRCdKnNDahX NEOFpSQzHbdF3HAHS71ufz4dN2hG7NzdeYCGKy0HJUh7bAvwxt1WYKMOt3Hv/RdsmYDT 5l0sbhYT4h1ih/RnUO5g5kQHW37/SxGyh1EMlzwdtUuyRZUr8qaN4TA0LxQxTm7ojcSW iv8lDVWDFFGxcztBCxl1ysGMUYOrlvkq1fkOmRJE3fwx1UbX4jgTsKsVo0jlITJ9RzTu fmDQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=fyJ+Y9O6; 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; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id s17si3936714pjp.26.2019.06.21.16.43.44; Fri, 21 Jun 2019 16:43:59 -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=@gmail.com header.s=20161025 header.b=fyJ+Y9O6; 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; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726145AbfFUXnN (ORCPT + 99 others); Fri, 21 Jun 2019 19:43:13 -0400 Received: from mail-lj1-f193.google.com ([209.85.208.193]:37758 "EHLO mail-lj1-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726045AbfFUXnN (ORCPT ); Fri, 21 Jun 2019 19:43:13 -0400 Received: by mail-lj1-f193.google.com with SMTP id 131so7403132ljf.4 for ; Fri, 21 Jun 2019 16:43:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=tmluSxzqhi5CcpOX2qxUxSbj+sNH9VpLrhtNj2D7dDA=; b=fyJ+Y9O6DdqVwOvEIXKf+lqUkhC4gruGlisZaVRnzqyHIqi5oFgHSCD5hfU8u72tpW f+mk6x3zSl2n8uP2mhyfdTgkqj4i7cU4fz+Znwd29vPXmqkiTcB+QntH7Y1HXsq0dSSZ eQfxFK9WeS3rd02Y1pFGg+cWYHErg/jkpNjyRIVQmO38sitxEAX6umJpRTfvCRHZRbkW fVLPd2XI7Rypm3N9YxQNqrZNm5mbPwV37hTHexFGoZQJ6NddVdw3Kbb5REnykG0PpybD IyISp5bgLBoIAVPSnqfuFCld8xVkP+zdiB9ZWlkArAKFHU8tOpeCv5zRmfuIUkIxm/mg 6VqQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=tmluSxzqhi5CcpOX2qxUxSbj+sNH9VpLrhtNj2D7dDA=; b=TTRVWfkO85IaR0KWHNMMBs1K2aQrX58RHeFPmdGeDMT3uHl9KbOmjI1vgynPkDYZ5R mqCw4u2+chjiV3EOorrdUvqE53+r319H7bUJMiCRJkUGZ2Vw7qY2HjkfTL5laKPYo8xa uguzsbt7vL/2ATHADWSdZV7PzuQbVZBuv7vT6YLhV7JFJDUk+5i+iUzTPX+S6uEE3eGh lETe20fMSEVrq8shQVMr+RCktMbOa1gpleOz4M+M2XXSlqcdcv2fsRrUIpQwdjaZHlj3 QR3Btz2XArHL7zFyLVJ0Pqx4lOIU/Z/SClmXPSphNQxJfu1PgVARHSLN9sfhYmB1oaQF ebdw== X-Gm-Message-State: APjAAAXJLjcxC43PMxh1pe3GJy7WKe3lFIyVJL0yxE+bpxzoYBHTZ1Kd W9hYbqiDL0z1u8tShMG7nLS19b8s+BJYJuh4unl66V3ZWg8= X-Received: by 2002:a2e:890a:: with SMTP id d10mr31837859lji.145.1561160591228; Fri, 21 Jun 2019 16:43:11 -0700 (PDT) MIME-Version: 1.0 References: <20190621214139.GA31034@kroah.com> <5a012e7c-cbed-c3a9-8d84-851de34630d8@valvesoftware.com> In-Reply-To: <5a012e7c-cbed-c3a9-8d84-851de34630d8@valvesoftware.com> From: Josh Hunt Date: Fri, 21 Jun 2019 16:42:59 -0700 Message-ID: Subject: Re: Steam is broken on new kernels To: "Pierre-Loup A. Griffais" Cc: Eric Dumazet , Linus Torvalds , Greg Kroah-Hartman , lkml Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jun 21, 2019 at 4:07 PM Pierre-Loup A. Griffais wrote: > > > > On 6/21/19 3:38 PM, Eric Dumazet wrote: > > Please look at my recent patch. > > Sorry I am travelling.... > > > > On Fri, Jun 21, 2019, 6:19 PM Linus Torvalds > > > > > wrote: > > > > On Fri, Jun 21, 2019 at 2:41 PM Greg Kroah-Hartman > > > wrote: > > > > > > What specific commit caused the breakage? > > > > Both on reddit and on github there seems to be confusion about whether > > it's a problem or not. Some people have it working with the exact same > > kernel that breaks for others. > > > > And then some people seem to say it works intermittently for them, > > which seems to indicate a timing issue. > > > > Looking at the SACK patches (assuming it's one of them), I'd suspect > > the "tcp: tcp_fragment() should apply sane memory limits". > > > > Eric, that one does > > > > if (unlikely((sk->sk_wmem_queued >> 1) > sk->sk_sndbuf)) { > > NET_INC_STATS(sock_net(sk), LINUX_MIB_TCPWQUEUETOOBIG); > > return -ENOMEM; > > } > > > > but I think it's *normal* for "sk_wmem_queued >> 1" to be around the > > same size as sk_sndbuf. So if there is some fragmentation, and we add > > more skb's to it, that would seem to trigger fairly easily. > > Particularly since this is all in "truesize" units, which can be a lot > > bigger than the packets themselves. > > > > I don't know the code, so I may be out to lunch and barking up > > completely the wrong tree, but that particular check does seem like it > > might trigger much more easily than I think the code _intended_ it to > > trigger? > > > > Pierre-Loup - do you guys have a test-case inside of valve? Or is this > > purely "we see some people with problems"? > > Definitely the latter, although the volume of complaints clearly points > to a real problem from our experience. Reproducing locally, bisecting > and testing possible fixes is just now starting on our end. > > I agree not all users seem affected; most affected people report success > by using -tcp to launch Steam, which makes it use direct TCP instead of > WebSockets, our current default connection method for Linux. > > Thanks, > - Pierre-Loup > > > > > Linus > > > I asked on the github thread if users seeing the problem could check the new wqueue too big counter: https://github.com/ValveSoftware/steam-for-linux/issues/6326 So far one person is seeing the counter increase when they see the problem, and another that doesn't see the problem has the counter at 0. Obviously not a great sample size, but hopefully more will report. If nothing else, someone is seeing the counter increase while trying to connect to steam. -- Josh