From: Weiming Shi <bestswngs@gmail.com>
To: Allison Henderson <achender@kernel.org>
Cc: netdev@vger.kernel.org, Paolo Abeni <pabeni@redhat.com>,
Jakub Kicinski <kuba@kernel.org>,
Eric Dumazet <edumazet@google.com>,
"David S . Miller" <davem@davemloft.net>,
linux-rdma@vger.kernel.org, rds-devel@oss.oracle.com,
Xiang Mei <xmei5@asu.edu>
Subject: Re: [PATCH net] net/rds: fix NULL deref in rds_ib_send_cqe_handler() on masked atomic completion
Date: Mon, 8 Jun 2026 14:36:32 +0800 [thread overview]
Message-ID: <aiZi3WoSSY8yN8JW@Air.local> (raw)
In-Reply-To: <73dcc08ff744364c097ec63bf81a26bd15e8f2af.camel@kernel.org>
On 26-06-07 12:32, Allison Henderson wrote:
> On Sat, 2026-06-06 at 12:24 -0700, Weiming Shi wrote:
> > rds_ib_xmit_atomic() always programs a masked atomic opcode
> > (IB_WR_MASKED_ATOMIC_CMP_AND_SWP or IB_WR_MASKED_ATOMIC_FETCH_AND_ADD)
> > for every RDS atomic cmsg. But the completion-side switch in
> > rds_ib_send_unmap_op() only handles the non-masked opcodes, so a masked
> > atomic completion falls through to default and returns rm == NULL while
> > send->s_op is left set. rds_ib_send_cqe_handler() then dereferences the
> > NULL rm via rm->m_final_op, oopsing in softirq context. An unprivileged
> > AF_RDS sendmsg() of an atomic cmsg over an active RDS/IB connection
> > triggers it; on hardware that natively accepts masked atomics (mlx4,
> > mlx5) no extra setup is needed.
> >
> > RDS/IB: rds_ib_send_unmap_op: unexpected opcode 0xd in WR!
> > Oops: general protection fault [#1] SMP KASAN
> > KASAN: null-ptr-deref in range [0x0000000000000190-0x0000000000000197]
> > RIP: rds_ib_send_cqe_handler+0x25c/0xb10 (net/rds/ib_send.c:282)
> > Call Trace:
> > <IRQ>
> > rds_ib_send_cqe_handler (net/rds/ib_send.c:282)
> > poll_scq (net/rds/ib_cm.c:274)
> > rds_ib_tasklet_fn_send (net/rds/ib_cm.c:294)
> > tasklet_action_common (kernel/softirq.c:943)
> > handle_softirqs (kernel/softirq.c:573)
> > run_ksoftirqd (kernel/softirq.c:479)
> > </IRQ>
> > Kernel panic - not syncing: Fatal exception in interrupt
> >
> > Handle the masked atomic opcodes in the same case as the non-masked
> > ones: they map to the same struct rds_message.atomic union member, so
> > the existing container_of()/rds_ib_send_unmap_atomic() body is correct
> > for them.
> >
> > Fixes: 20c72bd5f5f9 ("RDS: Implement masked atomic operations")
> > Reported-by: Xiang Mei <xmei5@asu.edu>
> > Assisted-by: Claude:claude-opus-4-8
> > Signed-off-by: Weiming Shi <bestswngs@gmail.com>
>
> Hi Weiming,
>
> Thanks for the thorough writeup, I've traced through the logic and the
> fix looks correct to me as do the tags. Thanks for catching this!
>
> Reviewed-by: Allison Henderson <achender@kernel.org>
> Allison
>
> > ---
> > net/rds/ib_send.c | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> > diff --git a/net/rds/ib_send.c b/net/rds/ib_send.c
> > index fcd04c29f543..d6be95542119 100644
> > --- a/net/rds/ib_send.c
> > +++ b/net/rds/ib_send.c
> > @@ -170,6 +170,8 @@ static struct rds_message *rds_ib_send_unmap_op(struct rds_ib_connection *ic,
> > break;
> > case IB_WR_ATOMIC_FETCH_AND_ADD:
> > case IB_WR_ATOMIC_CMP_AND_SWP:
> > + case IB_WR_MASKED_ATOMIC_FETCH_AND_ADD:
> > + case IB_WR_MASKED_ATOMIC_CMP_AND_SWP:
> > if (send->s_op) {
> > rm = container_of(send->s_op, struct rds_message, atomic);
> > rds_ib_send_unmap_atomic(ic, send->s_op, wc_status);
>
Thanks for your review.
prev parent reply other threads:[~2026-06-08 6:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-06 19:24 [PATCH net] net/rds: fix NULL deref in rds_ib_send_cqe_handler() on masked atomic completion Weiming Shi
2026-06-07 19:32 ` Allison Henderson
2026-06-08 6:36 ` Weiming Shi [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=aiZi3WoSSY8yN8JW@Air.local \
--to=bestswngs@gmail.com \
--cc=achender@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--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 \
--cc=xmei5@asu.edu \
/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