From: Leon Romanovsky <leon@kernel.org>
To: Yehyeong Lee <yhlee@isslab.korea.ac.kr>
Cc: Sagi Grimberg <sagi@grimberg.me>,
Max Gurtovoy <mgurtovoy@nvidia.com>,
Jason Gunthorpe <jgg@ziepe.ca>,
"Martin K . Petersen" <martin.petersen@oracle.com>,
Mike Christie <michael.christie@oracle.com>,
linux-rdma@vger.kernel.org, target-devel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v8 0/6] IB/isert: fix the device removal use-after-free
Date: Wed, 11 Nov 2026 15:24:26 +0200 [thread overview]
Message-ID: <20261111132426.GR8635@unreal> (raw)
In-Reply-To: <CAM+FBJen6v58uZPvSTfSG--9r9LzwAp1PBWbWK7RUFM89qmMJA@mail.gmail.com>
On Fri, Nov 06, 2026 at 08:26:49PM +0900, Yehyeong Lee wrote:
> Hi Leon,
>
> Sorry for the flood of versions. I should have waited for review instead
> of reposting every time the bot flagged something. I'll stop here and
> won't send another version unless someone asks for one.
>
> For what it's worth, each version was tested on soft-RoCE with KASAN,
> racing device removal against connect, login and teardown. I don't have
> iSER hardware, so none of it has run on a real HCA.
>
> If it helps, I can send 1/6 and 2/6 on their own, without the stable
> tag, and leave the rest until someone can test it on hardware. If you'd
> rather drop the series, that's fine too.
You should get Acked by from isert maintainers.
Thanks
prev parent reply other threads:[~2026-11-11 13:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 4:03 [PATCH v8 0/6] IB/isert: fix the device removal use-after-free Yehyeong Lee
2026-11-04 4:03 ` [PATCH v8 1/6] IB/isert: do not publish connections being released on a second list Yehyeong Lee
2026-11-04 4:24 ` sashiko-bot
2026-11-04 4:03 ` [PATCH v8 2/6] IB/isert: drain the QP without holding isert_conn->mutex Yehyeong Lee
2026-11-04 4:22 ` sashiko-bot
2026-11-04 4:03 ` [PATCH v8 3/6] IB/isert: tear connections down from an ib_client on device removal Yehyeong Lee
2026-11-04 4:33 ` sashiko-bot
2026-11-04 4:03 ` [PATCH v8 4/6] IB/isert: drop the promotion reference when a connection errors out Yehyeong Lee
2026-11-04 4:16 ` sashiko-bot
2026-11-04 4:03 ` [PATCH v8 5/6] IB/isert: do not build a new isert_device for a device being removed Yehyeong Lee
2026-11-04 4:20 ` sashiko-bot
2026-11-04 4:03 ` [PATCH v8 6/6] IB/isert: only reinstate a connection that reached full feature phase Yehyeong Lee
2026-11-04 4:29 ` sashiko-bot
2026-11-04 14:20 ` [PATCH v8 0/6] IB/isert: fix the device removal use-after-free Leon Romanovsky
2026-11-06 11:37 ` Yehyeong Lee
[not found] ` <CAM+FBJen6v58uZPvSTfSG--9r9LzwAp1PBWbWK7RUFM89qmMJA@mail.gmail.com>
2026-11-11 13:24 ` 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=20261111132426.GR8635@unreal \
--to=leon@kernel.org \
--cc=jgg@ziepe.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mgurtovoy@nvidia.com \
--cc=michael.christie@oracle.com \
--cc=sagi@grimberg.me \
--cc=target-devel@vger.kernel.org \
--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.