From: Jakub Kicinski <kuba@kernel•org>
To: David Howells <dhowells@redhat•com>
Cc: netdev@vger•kernel.org, linux-afs@lists•infradead.org,
horms@kernel•org, alok.a.tiwari@oracle•com, davem@davemloft•net,
marc.dionne@auristor•com, linux-kernel@vger•kernel.org,
security@1seal•org, stable@kernel•org, pabeni@redhat•com,
anderson@allelesecurity•com, jaltman@auristor•com,
edumazet@google•com
Subject: Re: [PATCH net 2/5] rxrpc: Fix use of wrong skb when comparing queued RESP challenge serial
Date: Mon, 23 Mar 2026 14:45:41 -0700 [thread overview]
Message-ID: <20260323144541.3ef887b7@kernel.org> (raw)
In-Reply-To: <1433905.1774080919@warthog.procyon.org.uk>
On Sat, 21 Mar 2026 08:15:19 +0000 David Howells wrote:
> Jakub Kicinski <kuba@kernel•org> wrote:
>
> > The review under --- is AI generated. It looks legit to me.
>
> I saw that there was one on patchwork, but I couldn't access it.
There's a 24h delay before results are public otherwise noobs spam
the list with 100 versions until the AI is happy.
next prev parent reply other threads:[~2026-03-23 21:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-19 15:01 [PATCH net 0/5] rxrpc: Miscellaneous fixes David Howells
2026-03-19 15:01 ` [PATCH net 1/5] rxrpc: Fix RxGK token loading to check bounds David Howells
2026-03-19 15:01 ` [PATCH net 2/5] rxrpc: Fix use of wrong skb when comparing queued RESP challenge serial David Howells
2026-03-21 1:45 ` Jakub Kicinski
2026-03-21 8:15 ` David Howells
2026-03-23 21:45 ` Jakub Kicinski [this message]
2026-03-23 21:51 ` David Howells
2026-03-23 22:11 ` Jakub Kicinski
2026-03-19 15:01 ` [PATCH net 3/5] rxrpc: Fix rack timer warning to report unexpected mode David Howells
2026-03-19 15:01 ` [PATCH net 4/5] rxrpc: Fix keyring reference count leak in rxrpc_setsockopt() David Howells
2026-03-19 15:01 ` [PATCH net 5/5] rxrpc: Fix key reference count leak from call->key David Howells
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=20260323144541.3ef887b7@kernel.org \
--to=kuba@kernel$(echo .)org \
--cc=alok.a.tiwari@oracle$(echo .)com \
--cc=anderson@allelesecurity$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=dhowells@redhat$(echo .)com \
--cc=edumazet@google$(echo .)com \
--cc=horms@kernel$(echo .)org \
--cc=jaltman@auristor$(echo .)com \
--cc=linux-afs@lists$(echo .)infradead.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=marc.dionne@auristor$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=security@1seal$(echo .)org \
--cc=stable@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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