From: David Howells <dhowells@redhat.com>
To: netdev@vger.kernel.org
Cc: David Howells <dhowells@redhat.com>,
Marc Dionne <marc.dionne@auristor.com>,
Yunsheng Lin <linyunsheng@huawei.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
linux-afs@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: [PATCH net-next 0/2] rxrpc: Fixes for AF_RXRPC
Date: Tue, 12 Mar 2024 23:37:16 +0000 [thread overview]
Message-ID: <20240312233723.2984928-1-dhowells@redhat.com> (raw)
Here are a couple of fixes for the AF_RXRPC changes[1] in net-next.
(1) Fix a runtime warning introduced by a patch that changed how
page_frag_alloc_align() works.
(2) Fix an is-NULL vs IS_ERR error handling bug.
The patches are tagged here:
git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git tags/rxrpc-iothread-20240312
And can be found on this branch:
http://git.kernel.org/cgit/linux/kernel/git/dhowells/linux-fs.git/log/?h=rxrpc-iothread
David
Link: https://lore.kernel.org/r/20240306000655.1100294-1-dhowells@redhat.com/ [1]
David Howells (2):
rxrpc: Fix use of changed alignment param to page_frag_alloc_align()
rxrpc: Fix error check on ->alloc_txbuf()
net/rxrpc/sendmsg.c | 4 ++--
net/rxrpc/txbuf.c | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
next reply other threads:[~2024-03-12 23:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-12 23:37 David Howells [this message]
2024-03-12 23:37 ` [PATCH net-next 1/2] rxrpc: Fix use of changed alignment param to page_frag_alloc_align() David Howells
2024-03-12 23:37 ` [PATCH net-next 2/2] rxrpc: Fix error check on ->alloc_txbuf() David Howells
2024-03-13 8:17 ` [PATCH net-next 0/2] rxrpc: Fixes for AF_RXRPC David Howells
2024-03-13 11:14 ` [PATCH net-next 1/2] rxrpc: Fix use of changed alignment param to page_frag_alloc_align() David Howells
2024-03-14 12:20 ` [PATCH net-next 0/2] rxrpc: Fixes for AF_RXRPC 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=20240312233723.2984928-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=linyunsheng@huawei.com \
--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
all inboxes | Powered by JetHome®