From: patchwork-bot+netdevbpf@kernel.org
To: Allison Henderson <achender@kernel.org>
Cc: netdev@vger.kernel.org, pabeni@redhat.com, edumazet@google.com,
rds-devel@oss.oracle.com, kuba@kernel.org, horms@kernel.org,
linux-rdma@vger.kernel.org
Subject: Re: [PATCH net v2 0/2] net/rds: Fix use-after-free in RDS/IB for non-init namespaces
Date: Sun, 12 Apr 2026 20:50:09 +0000 [thread overview]
Message-ID: <177602700979.3405581.15178712327198304598.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260408080420.540032-1-achender@kernel.org>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 8 Apr 2026 01:04:18 -0700 you wrote:
> This series fixes syzbot bug da8e060735ae02c8f3d1
> https://syzkaller.appspot.com/bug?extid=da8e060735ae02c8f3d1
>
> The report finds a use-after-free bug where ib connections access an
> invalid network namespace after it has been freed. The stack is:
>
> rds_rdma_cm_event_handler_cmn
> rds_conn_path_drop
> rds_destroy_pending
> check_net() <-- use-after-free
>
> [...]
Here is the summary with links:
- [net,v2,1/2] net/rds: Optimize rds_ib_laddr_check
https://git.kernel.org/netdev/net/c/236f718ac885
- [net,v2,2/2] net/rds: Restrict use of RDS/IB to the initial network namespace
https://git.kernel.org/netdev/net/c/ebf71dd4aff4
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-04-12 20:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-08 8:04 [PATCH net v2 0/2] net/rds: Fix use-after-free in RDS/IB for non-init namespaces Allison Henderson
2026-04-08 8:04 ` [PATCH net v2 1/2] net/rds: Optimize rds_ib_laddr_check Allison Henderson
2026-04-08 8:04 ` [PATCH net v2 2/2] net/rds: Restrict use of RDS/IB to the initial network namespace Allison Henderson
2026-04-12 20:50 ` 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=177602700979.3405581.15178712327198304598.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=achender@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rds-devel@oss.oracle.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