From: Zhu Yanjun <yanjun.zhu@linux.dev>
To: Leon Romanovsky <leon@kernel.org>, Li Zhijian <lizhijian@fujitsu.com>
Cc: linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org,
zyjzyj2000@gmail.com, jgg@ziepe.ca
Subject: Re: [PATCH] RDMA/rxe: Fix race condition in QP timer handlers
Date: Sun, 25 Jan 2026 13:24:39 -0800 [thread overview]
Message-ID: <c718d1c2-6c7e-47df-a3f4-097f7cadbbbf@linux.dev> (raw)
In-Reply-To: <20260125140812.GE13967@unreal>
在 2026/1/25 6:08, Leon Romanovsky 写道:
> On Tue, Jan 20, 2026 at 03:44:37PM +0800, Li Zhijian wrote:
>> I encontered the following warning:
>> WARNING: drivers/infiniband/sw/rxe/rxe_task.c:249 at rxe_sched_task+0x1c8/0x238 [rdma_rxe], CPU#0: swapper/0/0
>> ...
>> libsha1 [last unloaded: ip6_udp_tunnel]
>> CPU: 0 UID: 0 PID: 0 Comm: swapper/0 Tainted: G C 6.19.0-rc5-64k-v8+ #37 PREEMPT
>> Tainted: [C]=CRAP
>> Hardware name: Raspberry Pi 4 Model B Rev 1.2
>> Call trace:
>> rxe_sched_task+0x1c8/0x238 [rdma_rxe] (P)
>> retransmit_timer+0x130/0x188 [rdma_rxe]
>> call_timer_fn+0x68/0x4d0
>> __run_timers+0x630/0x888
>> ...
>> WARNING: drivers/infiniband/sw/rxe/rxe_task.c:38 at rxe_sched_task+0x1c0/0x238 [rdma_rxe], CPU#0: swapper/0/0
>> ...
>> WARNING: drivers/infiniband/sw/rxe/rxe_task.c:111 at do_work+0x488/0x5c8 [rdma_rxe], CPU#3: kworker/u17:4/93400
>> ...
>> refcount_t: underflow; use-after-free.
>> WARNING: lib/refcount.c:28 at refcount_warn_saturate+0x138/0x1a0, CPU#3: kworker/u17:4/93400
>>
>> The issue is caused by a race condition between retransmit_timer() and
>> rxe_destroy_qp, leading to the Queue Pair's (QP) reference count dropping
>> to zero during timer handler execution.
>>
>> It seems this warning is harmless because rxe_qp_do_cleanup() will flush
>> all pending timers and requests.
>>
>> Example of flow causing the issue:
>>
>> CPU0 CPU1
>> retransmit_timer() {
>> spin_lock_irqsave
>> rxe_destroy_qp()
>> __rxe_cleanup()
>> __rxe_put() // qp->ref_count decrease to 0
>> rxe_qp_do_cleanup() {
>> if (qp->valid) {
>> rxe_sched_task() {
>> WARN_ON(rxe_read(task->qp) <= 0);
>> }
>> }
>> spin_unlock_irqrestore
>> }
>> spin_lock_irqsave
>> qp->valid = 0
>> spin_unlock_irqrestore
>> }
>>
>> Ensure the QP's reference count is maintained and its validity is checked
>> within the timer callbacks by adding calls to rxe_get(qp) and corresponding
>> rxe_put(qp) after use.
>>
>> Signed-off-by: Li Zhijian <lizhijian@fujitsu.com>
>
> Fixes line?
The Fixes line should be the following?
Fixes: 8700e3e7c485 ("Soft RoCE driver")
Best Regards,
Zhu Yanjun
>
> Thanks
>
>> ---
>> drivers/infiniband/sw/rxe/rxe_comp.c | 3 +++
>> drivers/infiniband/sw/rxe/rxe_req.c | 3 +++
>> 2 files changed, 6 insertions(+)
next prev parent reply other threads:[~2026-01-25 21:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-20 7:44 [PATCH] RDMA/rxe: Fix race condition in QP timer handlers Li Zhijian
2026-01-21 5:04 ` Zhu Yanjun
2026-01-25 14:08 ` Leon Romanovsky
2026-01-25 21:24 ` Zhu Yanjun [this message]
2026-01-27 9:27 ` Zhijian Li (Fujitsu)
2026-01-28 10:02 ` Leon Romanovsky
2026-01-28 10:25 ` Leon Romanovsky
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=c718d1c2-6c7e-47df-a3f4-097f7cadbbbf@linux.dev \
--to=yanjun.zhu@linux.dev \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=lizhijian@fujitsu.com \
--cc=zyjzyj2000@gmail.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