From: Jakub Kicinski <kuba@kernel.org>
To: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
Cc: Paul Moses <p@1g4.org>, <netdev@vger.kernel.org>,
<magnus.karlsson@intel.com>, <sdf@fomichev.me>,
<davem@davemloft.net>, <edumazet@kernel.org>, <pabeni@redhat.com>,
<horms@kernel.org>, <bpf@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <stable@vger.kernel.org>
Subject: Re: [PATCH net] xsk: restore UMEM flags after failed pool assignment
Date: Fri, 23 Oct 2026 16:12:11 -0700 [thread overview]
Message-ID: <20261023161211.74b2acb6@kernel.org> (raw)
In-Reply-To: <atpDcGN3zWhixRj1@boxer>
On Thu, 22 Oct 2026 19:10:08 +0200 Maciej Fijalkowski wrote:
> > Right, evidence suggests igc handles it gracefully, I had attempted
> > to provide multiple examples of real world impact to satiate Sashiko,
> > but only igc survived final edit. It needs to be open for the failed
> > bind and successful retry, it can be closed after and bad state
> > remains. If you're looking for greater impact, look at stmmac. I'll
> > send out a v2 without naming drivers specifically soon.
>
> Not really needed to go with v2 with reworded message. Let us wait for
> bot reports first.
Bots look happy, but I'm slightly confused by Paul's "only igc survived
final edit" statement. Was this issue discovered in normal development
or by an LLM bug hunt? Was it tested on I225-V hardware, or LLM just
suggest that HW as a NIC that would be impacted?
next prev parent reply other threads:[~2026-10-23 23:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-21 22:47 Paul Moses
2026-10-22 8:34 ` Maciej Fijalkowski
2026-10-22 16:55 ` Paul Moses
2026-10-22 17:10 ` Maciej Fijalkowski
2026-10-23 23:12 ` Jakub Kicinski [this message]
2026-10-24 1:19 ` Paul Moses
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=20261023161211.74b2acb6@kernel.org \
--to=kuba@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.fijalkowski@intel.com \
--cc=magnus.karlsson@intel.com \
--cc=netdev@vger.kernel.org \
--cc=p@1g4.org \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
--cc=stable@vger.kernel.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
all inboxes | Powered by JetHome®