From: Jakub Kicinski <kuba@kernel.org>
To: David Howells <dhowells@redhat.com>
Cc: netdev@vger.kernel.org, Marc Dionne <marc.dionne@auristor.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
linux-afs@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v7 00/11] rxrpc: Fix CHALLENGE packet handling
Date: Mon, 17 Aug 2026 18:58:02 -0700 [thread overview]
Message-ID: <20260817185802.0aa4c9ee@kernel.org> (raw)
In-Reply-To: <20260812110129.979970-1-dhowells@redhat.com>
On Wed, 12 Aug 2026 12:01:15 +0100 David Howells wrote:
> - Fixed more Sashiko-reported bugs[7]:
> - Made the loops in afs_make_call() that call rxrpc_kernel_send_data()
> pass the amount left in the iterator rather than an unreducing size.
> - Made the second loop in afs_make_call() check to see if
> rxrpc_kernel_send_data() returned an error.
> - Removed yet more OOB references, two in linux/af_rxrpc.h and one in
> rxrpc.rst.
FWIW I had to kick off clashiko manually because sparse false-positives
on one of the patches. It should finish in 30min or so. I'm signing off
for the day, so please TAL if you can:
https://netdev-ai.bots.linux.dev/sashiko/#/patchset/20260812110129.979970-6-dhowells@redhat.com
and let us know if we should ship v7 as is or you want to tweak..
next prev parent reply other threads:[~2026-08-18 1:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-12 11:01 [PATCH net v7 00/11] rxrpc: Fix CHALLENGE packet handling David Howells
2026-08-12 11:01 ` [PATCH net v7 01/11] rxrpc: Fix sendmsg to not return an error if last packet queued David Howells
2026-08-12 11:01 ` [PATCH net v7 02/11] rxrpc: Fix sendmsg length David Howells
2026-08-12 11:01 ` [PATCH net v7 03/11] rxrpc: Fix packet encryption error handling David Howells
2026-08-12 11:01 ` [PATCH net v7 04/11] rxrpc: Fix update of call->tx_pending without holding lock David Howells
2026-08-12 11:01 ` [PATCH net v7 05/11] rxrpc: Fix generation of notifications after call completion David Howells
2026-08-12 11:01 ` [PATCH net v7 06/11] rxrpc: Expand abort trace enum David Howells
2026-08-12 11:01 ` [PATCH net v7 07/11] keys: Add refcounting to user-defined key type payload David Howells
2026-08-12 11:01 ` [PATCH net v7 08/11] afs: Create a server appdata key David Howells
2026-08-12 11:01 ` [PATCH net v7 09/11] rxrpc: Pass appdata key to rxrpc_call and thence to rxrpc_bundle David Howells
2026-08-12 11:01 ` [PATCH net v7 10/11] rxrpc: Fix CHALLENGE packet overqueuing and simplify RESPONSE generation David Howells
2026-08-12 11:01 ` [PATCH net v7 11/11] rxrpc: Remove OOB challenge/response code David Howells
2026-08-18 1:58 ` Jakub Kicinski [this message]
2026-08-18 13:03 ` [PATCH net v7 00/11] rxrpc: Fix CHALLENGE packet handling David Howells
2026-08-18 14:49 ` David Howells
2026-08-18 14:49 ` Jakub Kicinski
2026-08-18 15:05 ` David Howells
2026-08-18 14:58 ` 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=20260817185802.0aa4c9ee@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--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 \
/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