From: patchwork-bot+netdevbpf@kernel.org
To: Nguyen Ngoc Thang <ngocthang2710.1999@gmail.com>
Cc: achender@kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, 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: Tue, 20 Oct 2026 21:10:06 +0000 [thread overview]
Message-ID: <179253060652.212662.1082879291044254668.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261016161525.146537-1-ngocthang2710.1999@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 16 Oct 2026 23:15:25 +0700 you 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
>
> [...]
Here is the summary with links:
- net/rds: ib: don't enable IRQs in rds_ib_conn_free()
https://git.kernel.org/netdev/net-next/c/f6fa1d60ec3c
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-20 21:10 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-17 3:30 ` Allison Henderson
2026-10-20 21: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=179253060652.212662.1082879291044254668.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=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