From: Nguyen Ngoc Thang <ngocthang2710.1999@gmail.com>
To: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Cc: linux-block@vger.kernel.org, Daniel Wagner <dwagner@suse.de>,
Hannes Reinecke <hare@suse.de>,
linux-nvme@lists.infradead.org
Subject: Re: [PATCH blktests] nvme/071: add a test for fcloop LS request use-after-free
Date: Wed, 23 Sep 2026 20:53:16 +0700 [thread overview]
Message-ID: <20260923135316.13144-1-ngocthang2710.1999@gmail.com> (raw)
In-Reply-To: <arOLaz8NSnz6bqL2@shinmob>
Hi Shin'ichiro,
Thanks for testing and the review, v2 is sent:
[PATCH blktests v2] nvme/071: add a test for fcloop LS request use-after-free
Message-ID: <20260923134938.12673-1-ngocthang2710.1999@gmail.com>
- Noted the kernel fix's commit title in the file header, since it's not
applied yet and has no hash.
- local -a ports, and use _get_fc_host_port() instead of reading
ports_to_hosts directly.
- On the hang: I couldn't reproduce a real hang, but I think I found the
cause. _nvme_connect_subsys() doesn't pass --ctrl-loss-tmo, so it
defaults to NVMF_DEF_CTRL_LOSS_TMO (600s). After we pull the remote
port the host has nothing to reconnect to, and the following
_nvme_disconnect_subsys() has to wait on that reconnect state before
it can remove the controller, up to 10 minutes if it lands there.
v2 connects with --ctrl-loss-tmo 0 so the host gives up on the first
failed reconnect instead. Let me know if you still see it hang with
this.
- On the swept delay: I tried a fixed "sleep 0" here too and got the
same KASAN UAF + list_debug BUG as with the sweep, so it wasn't
earning its complexity. Dropped it in v2.
Thanks,
Thang
next prev parent reply other threads:[~2026-09-23 13:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 14:56 [PATCH blktests] nvme/071: add a test for fcloop LS request use-after-free Nguyen Ngoc Thang
2026-09-23 8:33 ` Shin'ichiro Kawasaki
2026-09-23 13:53 ` Nguyen Ngoc Thang [this message]
2026-09-23 13:49 ` [PATCH blktests v2] " Nguyen Ngoc Thang
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=20260923135316.13144-1-ngocthang2710.1999@gmail.com \
--to=ngocthang2710.1999@gmail.com \
--cc=dwagner@suse.de \
--cc=hare@suse.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=shinichiro.kawasaki@wdc.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