From: Allison Henderson <achender@kernel.org>
To: Nguyen Ngoc Thang <ngocthang2710.1999@gmail.com>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Cc: Simon Horman <horms@kernel.org>,
netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
rds-devel@oss.oracle.com, linux-kernel@vger.kernel.org,
syzbot+c3741bb338b5c6d6a4aa@syzkaller.appspotmail.com,
stable@vger.kernel.org
Subject: Re: [PATCH] net/rds: ib: don't enable IRQs in rds_ib_conn_free()
Date: Fri, 16 Oct 2026 20:30:58 -0700 [thread overview]
Message-ID: <d0f8499622c1b81505ecfafa4fd056840d5cfd89.camel@kernel.org> (raw)
In-Reply-To: <20261016161525.146537-1-ngocthang2710.1999@gmail.com>
On Fri, 2026-10-16 at 23:15 +0700, Nguyen Ngoc Thang wrote:
> __rds_conn_create() calls trans->conn_free() with rds_conn_lock held
> and IRQs disabled when it loses the race to insert a connection.
> rds_ib_conn_free() takes the device list lock with spin_lock_irq() and
> releases it with spin_unlock_irq(), so IRQs are turned on while
> rds_conn_lock is still held:
>
> raw_local_irq_restore() called with IRQs enabled
> WARNING: kernel/locking/irqflag-debug.c:10 at warn_bogus_irq_restore+0xc/0x20
> _raw_spin_unlock_irqrestore+0x67/0x80
> __rds_conn_create+0x1de5/0x2290
> rds_conn_create_outgoing+0x43/0x60
> rds_sendmsg+0xfca/0x20e0
> __sys_sendto+0x408/0x5a0
>
> It needs an RDS socket bound to an address on an RDMA device (e.g. rxe)
> and two concurrent sendto() calls to the same new destination.
>
> The TCP and loopback ->conn_free() callbacks already use irqsave, so
> do the same here.
>
> Fixes: 745cbccac3fe ("RDS: Rewrite connection cleanup, fixing oops on rmmod")
> Reported-by: syzbot+c3741bb338b5c6d6a4aa@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=c3741bb338b5c6d6a4aa
> Cc: stable@vger.kernel.org
> Signed-off-by: Nguyen Ngoc Thang <ngocthang2710.1999@gmail.com>
Hi Nguyen,
Thanks for the fix. This is the same change as patch 1 of the
connection-lifetime series pending for net-next ("net/rds: ib: don't
enable interrupts in rds_ib_conn_free()"). But that's a much bigger set
that's been churning for a while. Since yours is stand alone with the
syzbot report for net, it's fine for yours to go first. I'll drop my
patch 1 when your patch lands.
Reviewed-by: Allison Henderson <achender@kernel.org>
Thanks!
Allison
> ---
> net/rds/ib_cm.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/net/rds/ib_cm.c b/net/rds/ib_cm.c
> index 6e3110a04ae6..5c717120eab5 100644
> --- a/net/rds/ib_cm.c
> +++ b/net/rds/ib_cm.c
> @@ -1271,6 +1271,7 @@ void rds_ib_conn_free(void *arg)
> {
> struct rds_ib_connection *ic = arg;
> spinlock_t *lock_ptr;
> + unsigned long flags;
>
> rdsdebug("ic %p\n", ic);
>
> @@ -1281,9 +1282,10 @@ void rds_ib_conn_free(void *arg)
> */
> lock_ptr = ic->rds_ibdev ? &ic->rds_ibdev->spinlock : &ib_nodev_conns_lock;
>
> - spin_lock_irq(lock_ptr);
> + /* May be called with IRQs already disabled (see __rds_conn_create()) */
> + spin_lock_irqsave(lock_ptr, flags);
> list_del(&ic->ib_node);
> - spin_unlock_irq(lock_ptr);
> + spin_unlock_irqrestore(lock_ptr, flags);
>
> rds_ib_recv_free_caches(ic);
>
prev parent reply other threads:[~2026-10-17 3:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 16:15 [PATCH] net/rds: ib: don't enable IRQs in rds_ib_conn_free() Nguyen Ngoc Thang
2026-10-16 16:25 ` sashiko-bot
2026-10-17 3:30 ` Allison Henderson [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=d0f8499622c1b81505ecfafa4fd056840d5cfd89.camel@kernel.org \
--to=achender@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ngocthang2710.1999@gmail.com \
--cc=pabeni@redhat.com \
--cc=rds-devel@oss.oracle.com \
--cc=stable@vger.kernel.org \
--cc=syzbot+c3741bb338b5c6d6a4aa@syzkaller.appspotmail.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