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, ljp1205831794@gmail.com, henrymei@tencent.com
Subject: Re: [PATCH net v4 0/2] net/rds: RDMA-CM event handler fixes for non-IB devices
Date: Mon, 12 Oct 2026 16:20:05 +0000 [thread overview]
Message-ID: <179182200552.3524695.4623096369791034138.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261003163408.250568-1-achender@kernel.org>
Hello:
This series was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Sat, 3 Oct 2026 09:34:06 -0700 you wrote:
> Hi all,
>
> This is v4 of Aohan Mei's fix for the uninitialized transport pointer
> in the RDMA-CM event handler (v1 at [1], v2 at [2], v3 at [3]), now a
> two-patch set.
>
> Patch 1 is the fix itself. v3 only rejected a connect request
> arriving on a non-IB device; the active side can bind an id to one
> as well, and resolving a route on an iWARP id leaves
> cm_id->route.path_rec unset, which the ROUTE_RESOLVED case
> dereferences. Such a connection is now dropped at ADDR_RESOLVED
> instead of resolving a route.
>
> [...]
Here is the summary with links:
- [net,v4,1/2] net: rds: fix uninitialized trans dereference in CM event handler
https://git.kernel.org/netdev/net/c/492ba6ac1b1f
- [net,v4,2/2] net/rds: don't let the rdma_cm destroy an id RDS still owns on route failure
https://git.kernel.org/netdev/net/c/98d446b7c013
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-10-12 16:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-03 16:34 [PATCH net v4 0/2] net/rds: RDMA-CM event handler fixes for non-IB devices Allison Henderson
2026-10-03 16:34 ` [PATCH net v4 1/2] net: rds: fix uninitialized trans dereference in CM event handler Allison Henderson
2026-10-03 17:56 ` sashiko-bot
2026-10-03 16:34 ` [PATCH net v4 2/2] net/rds: don't let the rdma_cm destroy an id RDS still owns on route failure Allison Henderson
2026-10-03 17:56 ` sashiko-bot
2026-10-12 16:20 ` 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=179182200552.3524695.4623096369791034138.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=achender@kernel.org \
--cc=edumazet@google.com \
--cc=henrymei@tencent.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=ljp1205831794@gmail.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