Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Guixin Liu <kanie@linux.alibaba.com>
To: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Cc: Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@kernel.dk>,
	Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
	Hannes Reinecke <hare@suse.de>,
	nilay@linux.ibm.com, Chaitanya Kulkarni <kch@nvidia.com>,
	Kanchan Joshi <joshi.k@samsung.com>,
	linux-nvme@lists.infradead.org
Subject: Re: [PATCH v2] nvme/070: add a test for Identify CNS 07h NULL pointer dereference
Date: Wed, 16 Sep 2026 19:40:08 +0800	[thread overview]
Message-ID: <c31cb0a3-cf24-458f-b77c-a97530963914@linux.alibaba.com> (raw)
In-Reply-To: <ansFVrVVtnxfhi0Y@shinmob>



在 2026/8/11 19:21, Shin'ichiro Kawasaki 写道:
> On Aug 04, 2026 / 10:46, Guixin Liu wrote:
>> nvmet_execute_identify_nslist() handles both the Active Namespace ID list
>> (CNS 02h) and the per-command-set variant (CNS 07h). For CNS 07h it
>> filtered the list on req->ns->csi, but this handler never resolves
>> req->ns, so it is always NULL. As soon as an enabled namespace with an
>> NSID above the requested value exists, the target dereferenced a NULL
>> pointer and oopsed.
>>
>> This test connects a target with a single namespace and issues an
>> Identify with CNS 07h starting from NSID 0, which is exactly the
>> condition that triggered the crash. Without the kernel fix [0] the target
>> oopses; with it the command completes normally.
>>
>> [0] https://lore.kernel.org/linux-nvme/20260730043105.3071328-2-kanie@linux.alibaba.com/
>>
>> Suggested-by: Christoph Hellwig <hch@lst.de>
>> Signed-off-by: Guixin Liu <kanie@linux.alibaba.com>
>> ---
>> v1 -> v2:
>>    - Use "nvme list-ns --csi=0" instead of a raw admin-passthru to issue
>>      Identify CNS 07h, as suggested by Nilay and Shinichiro; it drives the
>>      same target code path via the existing nvme-cli subcommand.
> Thanks for this v2 patch. It looks good to me. I will wait for the kernel side
> fix get settled on Linus master branch before I apply this patch.
Hi Shin'ichiro, the kernel side fix patch is already applied to master,
could you please apply this patch?

Best Regards,
Guixin Liu


  reply	other threads:[~2026-09-16 11:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-04  2:46 [PATCH v2] nvme/070: add a test for Identify CNS 07h NULL pointer dereference Guixin Liu
2026-08-04  4:48 ` Nilay Shroff
2026-08-04  7:32 ` Hannes Reinecke
2026-08-11 11:21 ` Shin'ichiro Kawasaki
2026-09-16 11:40   ` Guixin Liu [this message]
2026-09-17  8:01     ` Shin'ichiro Kawasaki

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=c31cb0a3-cf24-458f-b77c-a97530963914@linux.alibaba.com \
    --to=kanie@linux.alibaba.com \
    --cc=axboe@kernel.dk \
    --cc=hare@suse.de \
    --cc=hch@lst.de \
    --cc=joshi.k@samsung.com \
    --cc=kbusch@kernel.org \
    --cc=kch@nvidia.com \
    --cc=linux-nvme@lists.infradead.org \
    --cc=nilay@linux.ibm.com \
    --cc=sagi@grimberg.me \
    --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