From: patchwork-bot+netdevbpf@kernel.org
To: Allison Henderson <achender@kernel.org>
Cc: netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
pabeni@redhat.com, edumazet@google.com, kuba@kernel.org,
horms@kernel.org, jhubbard@nvidia.com, leon@kernel.org
Subject: Re: [PATCH net v4 0/4] net/rds: Bug fix ports
Date: Wed, 05 Aug 2026 01:10:11 +0000 [thread overview]
Message-ID: <178589221139.3859963.4972940145974971539.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260730041629.3512480-1-achender@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 29 Jul 2026 21:16:25 -0700 you wrote:
> Hi all,
>
> This is a small set of net/rds bug fixes and ports from uek to upstream
> rds. I've been working on extending the rds selftest case, but need to
> stabilize a few more bugs and the first few fall into net with Fixes
> tags. I decided to leverage fable for this set and I thought the ports we
> clean and well explained.
>
> [...]
Here is the summary with links:
- [net,v4,1/4] net/rds: don't use unpin_user_pages_dirty_lock() from atomic context
https://git.kernel.org/netdev/net-next/c/d100966325f7
- [net,v4,2/4] net/rds: hold the socket while an rds_mr references it
https://git.kernel.org/netdev/net-next/c/9079adef042c
- [net,v4,3/4] net/rds: fix rds_message leak in the rds_send_xmit() drop path
https://git.kernel.org/netdev/net-next/c/eb8a59a17f4a
- [net,v4,4/4] net/rds: unpin MR pages with unpin_user_pages_dirty_lock()
https://git.kernel.org/netdev/net-next/c/a507023e6ff1
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-08-05 1:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-30 4:16 [PATCH net v4 0/4] net/rds: Bug fix ports Allison Henderson
2026-07-30 4:16 ` [PATCH net v4 1/4] net/rds: don't use unpin_user_pages_dirty_lock() from atomic context Allison Henderson
2026-07-30 4:16 ` [PATCH net v4 2/4] net/rds: hold the socket while an rds_mr references it Allison Henderson
2026-07-30 4:16 ` [PATCH net v4 3/4] net/rds: fix rds_message leak in the rds_send_xmit() drop path Allison Henderson
2026-07-30 4:16 ` [PATCH net v4 4/4] net/rds: unpin MR pages with unpin_user_pages_dirty_lock() Allison Henderson
2026-08-05 1:02 ` [PATCH net v4 0/4] net/rds: Bug fix ports Jakub Kicinski
2026-08-05 4:30 ` Allison Henderson
2026-08-05 1:10 ` patchwork-bot+netdevbpf [this message]
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=178589221139.3859963.4972940145974971539.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=achender@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jhubbard@nvidia.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.