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 15:11:37 -0700 [thread overview]
Message-ID: <20260323151137.2fff6da3@kernel.org> (raw)
In-Reply-To: <3585122.1774302668@warthog.procyon.org.uk>
On Mon, 23 Mar 2026 21:51:08 +0000 David Howells wrote:
> Btw, do you know how to credit the AI site with reporting something? For
> instance for syzbot gives me a Reported-by: line that carries something that
> can be used as an email address. There were other things in the AI report,
> some of which I added patches for.
I was also wondering about that. syzbot reports are for stuff that's
already committed. Most of the CI and AI reports are pre-commit.
IDK if we have a way to attribute issues caught before commits go in.
I guess AI reviews are an integral part of the process now. We don't
have a tag for when reviewers/maintainers catch bugs in patches either.
next prev parent reply other threads:[~2026-03-23 22:11 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
2026-03-23 21:51 ` David Howells
2026-03-23 22:11 ` Jakub Kicinski [this message]
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=20260323151137.2fff6da3@kernel.org \
--to=kuba@kernel.org \
--cc=alok.a.tiwari@oracle.com \
--cc=anderson@allelesecurity.com \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jaltman@auristor.com \
--cc=linux-afs@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.dionne@auristor.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=security@1seal.org \
--cc=stable@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