From: Jakub Kicinski <kuba@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Thomas Zimmermann <tzimmermann@suse.de>,
Simona Vetter <simona@ffwll.ch>, Dave Airlie <airlied@gmail.com>,
davem@davemloft.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, pabeni@redhat.com,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [GIT PULL] Networking for v6.16-rc6 (follow up)
Date: Fri, 11 Jul 2025 12:34:44 -0700 [thread overview]
Message-ID: <20250711123444.71747051@kernel.org> (raw)
In-Reply-To: <CAHk-=whMyX44=Ga_nK-XUffhFH47cgVd2M_Buhi_b+Lz1jV5oQ@mail.gmail.com>
On Fri, 11 Jul 2025 12:30:28 -0700 Linus Torvalds wrote:
> > I spent several hours yesterday chasing all the wrong things (because
> > I thought it was in drm), and often thought "Oh, that fixed it". Only
> > to then realize that nope, the problem still happens.
> >
> > I will test the reverts. Several times.
>
> Well, the first boot with those three commits reverted shows no problem at all.
>
> But as mentioned, I've now had "Oh, that fixed it" about ten times.
>
> So that "Oh, it worked this time" has been tainted by past experience.
> Will do several more boots now in the hope that it's gone for good.
Fingers crossed. FWIW /proc/net/netlink should show the socket
drop counters. But my laptop running 6.15 has a number of
GNOME apps which never read their sockets so it's not going to
be as immediately obvious whether we regressed or its a bad app
as I hoped.
next prev parent reply other threads:[~2025-07-11 19:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-11 15:10 [GIT PULL] Networking for v6.16-rc6 (follow up) Jakub Kicinski
2025-07-11 17:44 ` pr-tracker-bot
2025-07-11 18:33 ` Linus Torvalds
2025-07-11 18:46 ` Jakub Kicinski
2025-07-11 18:54 ` Linus Torvalds
2025-07-11 19:18 ` Linus Torvalds
2025-07-11 19:30 ` Linus Torvalds
2025-07-11 19:34 ` Jakub Kicinski [this message]
2025-07-11 19:42 ` Linus Torvalds
2025-07-11 19:53 ` Jakub Kicinski
2025-07-11 20:07 ` Linus Torvalds
2025-07-11 20:35 ` Linus Torvalds
2025-07-11 21:46 ` Linus Torvalds
2025-07-11 22:19 ` Linus Torvalds
2025-07-11 23:58 ` Nam Cao
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250711123444.71747051@kernel.org \
--to=kuba@kernel.org \
--cc=airlied@gmail.com \
--cc=davem@davemloft.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=simona@ffwll.ch \
--cc=torvalds@linux-foundation.org \
--cc=tzimmermann@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.