All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Yehyeong Lee" <yhlee@isslab.korea.ac.kr>
Cc: linux-rdma@vger.kernel.org
Subject: Re: [PATCH v6 2/6] IB/isert: drain the QP without holding isert_conn->mutex
Date: Tue, 03 Nov 2026 23:00:58 +0000	[thread overview]
Message-ID: <sashiko-outbox-196170@kernel.org> (raw)
In-Reply-To: <20261103223802.1697607-3-yhlee@isslab.korea.ac.kr>

> isert_disconnected_handler() drains the QP with isert_conn->mutex held.
> The drain waits for the flush completions of the send and receive queues,
> and those are reaped by ib_cq_poll_work() on ib-comp-wq, where
> isert_login_recv_done() takes isert_conn->mutex before it looks at the
> connection state.  If a login receive completes while the handler holds
> the mutex, the completion handler blocks on the mutex and the drain blocks
> on the completion that handler would have reaped.
> 
> Return from isert_conn_terminate() whether this caller moved the
> connection to ISER_CONN_TERMINATING, and drain after dropping
> isert_conn->mutex.  Only the owner of isert_conn->node drains, so two
> callers cannot drain the same QP; the send and receive queues reserve room
> for one drain each, and a second concurrent drain hits the WARN_ONCE in
> __ib_drain_sq() and returns without draining.
> 
> [ ... ]
>    </TASK>
> 
> Fixes: 6d1fba0c2cc7 ("iser-target: Rework connection termination")
> Cc: stable@vger.kernel.org
> Signed-off-by: Yehyeong Lee <yhlee@isslab.korea.ac.kr>

Sashiko has reviewed this patch and found no issues.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261103223802.1697607-1-yhlee@isslab.korea.ac.kr?part=2


  reply	other threads:[~2026-11-03 23:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-03 22:37 [PATCH v6 0/6] IB/isert: fix the device removal use-after-free Yehyeong Lee
2026-11-03 22:37 ` [PATCH v6 1/6] IB/isert: do not publish connections being released on a second list Yehyeong Lee
2026-11-03 22:59   ` sashiko-bot
2026-11-03 22:37 ` [PATCH v6 2/6] IB/isert: drain the QP without holding isert_conn->mutex Yehyeong Lee
2026-11-03 23:00   ` sashiko-bot [this message]
2026-11-03 22:37 ` [PATCH v6 3/6] IB/isert: tear connections down from an ib_client on device removal Yehyeong Lee
2026-11-03 23:07   ` sashiko-bot
2026-11-03 22:38 ` [PATCH v6 4/6] IB/isert: drop the promotion reference when a connection errors out Yehyeong Lee
2026-11-03 23:00   ` sashiko-bot
2026-11-03 22:38 ` [PATCH v6 5/6] IB/isert: do not build a new isert_device for a device being removed Yehyeong Lee
2026-11-03 23:10   ` sashiko-bot
2026-11-03 22:38 ` [PATCH v6 6/6] IB/isert: only reinstate a connection that reached full feature phase Yehyeong Lee
2026-11-03 23:14   ` sashiko-bot
2026-11-04  1:23 ` [PATCH v6 0/6] IB/isert: fix the device removal use-after-free Yehyeong Lee

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=sashiko-outbox-196170@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=yhlee@isslab.korea.ac.kr \
    /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.