From: David Howells <dhowells@redhat.com>
To: netdev@vger.kernel.org
Cc: David Howells <dhowells@redhat.com>,
Marc Dionne <marc.dionne@auristor.com>,
Jakub Kicinski <kuba@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
linux-afs@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: [PATCH net 0/2] rxrpc: Miscellaneous fixes
Date: Mon, 7 Jul 2025 11:24:32 +0100 [thread overview]
Message-ID: <20250707102435.2381045-1-dhowells@redhat.com> (raw)
Here are some miscellaneous fixes for rxrpc:
(1) Fix a warning about over-large frame size in rxrpc_send_response().
(2) Fix assertion failure due to preallocation collision.
David
The patches can be found here also:
http://git.kernel.org/cgit/linux/kernel/git/dhowells/linux-fs.git/log/?h=rxrpc-fixes
David Howells (2):
rxrpc: Fix over large frame size warning
rxrpc: Fix bug due to prealloc collision
net/rxrpc/ar-internal.h | 15 +++++++++------
net/rxrpc/call_accept.c | 2 ++
net/rxrpc/output.c | 5 ++++-
3 files changed, 15 insertions(+), 7 deletions(-)
next reply other threads:[~2025-07-07 10:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-07 10:24 David Howells [this message]
2025-07-07 10:24 ` [PATCH net 1/2] rxrpc: Fix over large frame size warning David Howells
2025-07-07 10:24 ` [PATCH net 2/2] rxrpc: Fix bug due to prealloc collision David Howells
2025-07-08 19:03 ` Jakub Kicinski
2025-07-08 19:57 ` David Howells
2025-07-08 20:20 ` [PATCH net 0/2] rxrpc: Miscellaneous fixes patchwork-bot+netdevbpf
-- strict thread matches above, loose matches on Subject: below --
2025-02-03 11:03 David Howells
2025-02-04 14:40 ` patchwork-bot+netdevbpf
2024-10-01 13:26 David Howells
2024-10-03 23:40 ` patchwork-bot+netdevbpf
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=20250707102435.2381045-1-dhowells@redhat.com \
--to=dhowells@redhat.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@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