From: Leon Romanovsky <leon@kernel.org>
To: Gui-Dong Han <hanguidong02@gmail.com>
Cc: "yanjun.zhu" <yanjun.zhu@linux.dev>,
zyjzyj2000@gmail.com, jgg@ziepe.ca, linux-rdma@vger.kernel.org,
linux-kernel@vger.kernel.org, baijiaju1990@gmail.com,
stable@vger.kernel.org,
"rpearsonhpe@gmail.com" <rpearsonhpe@gmail.com>
Subject: Re: [PATCH] RDMA/rxe: Fix race in do_task() when draining
Date: Thu, 18 Sep 2025 15:10:54 +0300 [thread overview]
Message-ID: <20250918121054.GF10800@unreal> (raw)
In-Reply-To: <CAOPYjvZ-kn98bq0C_ng1e4hrC2LKh5jdo-fm1BB9M2ULbhp10A@mail.gmail.com>
On Thu, Sep 18, 2025 at 08:02:04PM +0800, Gui-Dong Han wrote:
> On Thu, Sep 18, 2025 at 5:58 PM Leon Romanovsky <leon@kernel.org> wrote:
> >
> > On Wed, Sep 17, 2025 at 12:30:56PM -0700, yanjun.zhu wrote:
> > > On 9/17/25 3:06 AM, Gui-Dong Han wrote:
> > > > When do_task() exhausts its RXE_MAX_ITERATIONS budget, it unconditionally
> > >
> > > From the source code, it will check ret value, then set it to
> > > TASK_STATE_IDLE, not unconditionally.
> > >
> > > > sets the task state to TASK_STATE_IDLE to reschedule. This overwrites
> > > > the TASK_STATE_DRAINING state that may have been concurrently set by
> > > > rxe_cleanup_task() or rxe_disable_task().
> > >
> > > From the source code, there is a spin lock to protect the state. It will not
> > > make race condition.
> > >
> > > >
> > > > This race condition breaks the cleanup and disable logic, which expects
> > > > the task to stop processing new work. The cleanup code may proceed while
> > > > do_task() reschedules itself, leading to a potential use-after-free.
> > > >
> > >
> > > Can you post the call trace when this problem occurred?
> > >
> > > Hi, Jason && Leon
> > >
> > > Please comment on this problem.
> >
> > The idea to recheck task->state looks correct to me, otherwise we overwrite it unconditionally.
> > However I would write this patch slightly different (without cont = 1):
> >
> > diff --git a/drivers/infiniband/sw/rxe/rxe_task.c b/drivers/infiniband/sw/rxe/rxe_task.c
> > index 6f8f353e95838..2ff5d7cc0a933 100644
> > --- a/drivers/infiniband/sw/rxe/rxe_task.c
> > +++ b/drivers/infiniband/sw/rxe/rxe_task.c
> > @@ -132,8 +132,10 @@ static void do_task(struct rxe_task *task)
> > * yield the cpu and reschedule the task
> > */
> > if (!ret) {
> > - task->state = TASK_STATE_IDLE;
> > - resched = 1;
> > + if (task->state != TASK_STATE_DRAINING) {
> > + task->state = TASK_STATE_IDLE;
> > + resched = 1;
> > + }
> > goto exit;
> > }
> >
> > @@ -151,7 +153,6 @@ static void do_task(struct rxe_task *task)
> > break;
> >
> > case TASK_STATE_DRAINING:
> > - task->state = TASK_STATE_DRAINED;
> > break;
> >
> > default:
> > (END)
>
> Hi Leon,
>
> Thanks for your review and for confirming the need for a fix.
>
> Regarding your suggested patch, I believe removing the transition to
> TASK_STATE_DRAINED would cause an issue. As seen in the code and comments
> for rxe_cleanup_task() and is_done(), the cleanup process waits for the
> final TASK_STATE_DRAINED state. If the task remains stuck in DRAINING,
> the cleanup loop will never terminate.
>
> My use of cont = 1 was intended as a minimal change. Since this
> regression was introduced during the migration from tasklets, restoring
> the pre-migration logic seemed like a reasonable approach. An alternative
> could be to set the state to TASK_STATE_DRAINED directly inside the
> if (!ret) block, and I am open to discussing the best fix.
Ahh, sorry, I misread that it is TASK_STATE_DRAINED and not TASK_STATE_DRAINING.
Thanks
>
> Regards,
> Han
prev parent reply other threads:[~2025-09-18 12:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-17 10:06 [PATCH] RDMA/rxe: Fix race in do_task() when draining Gui-Dong Han
2025-09-17 19:30 ` yanjun.zhu
2025-09-18 2:21 ` Gui-Dong Han
2025-09-18 16:31 ` Yanjun.Zhu
2025-09-19 3:15 ` Gui-Dong Han
2025-09-18 9:58 ` Leon Romanovsky
2025-09-18 12:02 ` Gui-Dong Han
2025-09-18 12:10 ` Leon Romanovsky [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=20250918121054.GF10800@unreal \
--to=leon@kernel.org \
--cc=baijiaju1990@gmail.com \
--cc=hanguidong02@gmail.com \
--cc=jgg@ziepe.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=rpearsonhpe@gmail.com \
--cc=stable@vger.kernel.org \
--cc=yanjun.zhu@linux.dev \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.