From: Jakub Kicinski <kuba@kernel.org>
To: torvalds@linux-foundation.org
Cc: davem@davemloft.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, pabeni@redhat.com
Subject: Re: [GIT PULL] Networking for v6.17-rc3
Date: Thu, 21 Aug 2025 10:37:50 -0700 [thread overview]
Message-ID: <20250821103750.252c2126@kernel.org> (raw)
In-Reply-To: <20250821102721.6deae493@kernel.org>
On Thu, 21 Aug 2025 10:27:21 -0700 Jakub Kicinski wrote:
> On Thu, 21 Aug 2025 10:16:41 -0700 Jakub Kicinski wrote:
> > Hi Linus!
>
> FWIW I'm hitting the splat below from random code paths (futex, epoll,
> bpf) when running your tree within Meta. Takes some time to hit, IDK
> what exactly triggers it. Could be a driver tho I can hit it on two
> different generations of servers.
Looks like it's this FWIW, so it's known
https://lore.kernel.org/all/68a2decd.050a0220.e29e5.009a.GAE@google.com/
next prev parent reply other threads:[~2025-08-21 17:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-21 17:16 [GIT PULL] Networking for v6.17-rc3 Jakub Kicinski
2025-08-21 17:27 ` Jakub Kicinski
2025-08-21 17:37 ` Jakub Kicinski [this message]
2025-08-21 18:20 ` pr-tracker-bot
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=20250821103750.252c2126@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=torvalds@linux-foundation.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox