Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ming Lei <ming.lei@redhat.com>
To: Keith Busch <kbusch@meta.com>
Cc: linux-nvme@lists.infradead.org, hch@lst.de,
	chaitanyak@nvidia.com, Keith Busch <kbusch@kernel.org>,
	Casey Chen <cachen@purestorage.com>
Subject: Re: [PATCH] nvme: fix admin request_queue lifetime
Date: Wed, 5 Nov 2025 09:20:31 +0800	[thread overview]
Message-ID: <aQqmX04KSNE-xctU@fedora> (raw)
In-Reply-To: <20251104225939.3641605-1-kbusch@meta.com>

On Tue, Nov 04, 2025 at 02:59:39PM -0800, Keith Busch wrote:
> From: Keith Busch <kbusch@kernel.org>
> 
> The namespaces can access the controller's admin request_queue, and
> stale references on the namespaces may exist. Ensure the request_queue
> is active by moving the controller's 'put' after all references on the
> controller have been released to ensure no one is trying to access the
> request_queue. This fixes a reported use-after-free bug:
> 
>   BUG: KASAN: slab-use-after-free in blk_queue_enter+0x41c/0x4a0
>   Read of size 8 at addr ffff88c0a53819f8 by task nvme/3287
>   CPU: 67 UID: 0 PID: 3287 Comm: nvme Tainted: G            E       6.13.2-ga1582f1a031e #15
>   Tainted: [E]=UNSIGNED_MODULE
>   Hardware name: Jabil /EGS 2S MB1, BIOS 1.00 06/18/2025
>   Call Trace:
>    <TASK>
>    dump_stack_lvl+0x4f/0x60
>    print_report+0xc4/0x620
>    ? _raw_spin_lock_irqsave+0x70/0xb0
>    ? _raw_read_unlock_irqrestore+0x30/0x30
>    ? blk_queue_enter+0x41c/0x4a0
>    kasan_report+0xab/0xe0
>    ? blk_queue_enter+0x41c/0x4a0
>    blk_queue_enter+0x41c/0x4a0
>    ? __irq_work_queue_local+0x75/0x1d0
>    ? blk_queue_start_drain+0x70/0x70
>    ? irq_work_queue+0x18/0x20
>    ? vprintk_emit.part.0+0x1cc/0x350
>    ? wake_up_klogd_work_func+0x60/0x60
>    blk_mq_alloc_request+0x2b7/0x6b0
>    ? __blk_mq_alloc_requests+0x1060/0x1060
>    ? __switch_to+0x5b7/0x1060
>    nvme_submit_user_cmd+0xa9/0x330
>    nvme_user_cmd.isra.0+0x240/0x3f0
>    ? force_sigsegv+0xe0/0xe0
>    ? nvme_user_cmd64+0x400/0x400
>    ? vfs_fileattr_set+0x9b0/0x9b0
>    ? cgroup_update_frozen_flag+0x24/0x1c0
>    ? cgroup_leave_frozen+0x204/0x330
>    ? nvme_ioctl+0x7c/0x2c0
>    blkdev_ioctl+0x1a8/0x4d0
>    ? blkdev_common_ioctl+0x1930/0x1930
>    ? fdget+0x54/0x380
>    __x64_sys_ioctl+0x129/0x190
>    do_syscall_64+0x5b/0x160
>    entry_SYSCALL_64_after_hwframe+0x4b/0x53
>   RIP: 0033:0x7f765f703b0b
>   Code: ff ff ff 85 c0 79 9b 49 c7 c4 ff ff ff ff 5b 5d 4c 89 e0 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d dd 52 0f 00 f7 d8 64 89 01 48
>   RSP: 002b:00007ffe2cefe808 EFLAGS: 00000202 ORIG_RAX: 0000000000000010
>   RAX: ffffffffffffffda RBX: 00007ffe2cefe860 RCX: 00007f765f703b0b
>   RDX: 00007ffe2cefe860 RSI: 00000000c0484e41 RDI: 0000000000000003
>   RBP: 0000000000000000 R08: 0000000000000003 R09: 0000000000000000
>   R10: 00007f765f611d50 R11: 0000000000000202 R12: 0000000000000003
>   R13: 00000000c0484e41 R14: 0000000000000001 R15: 00007ffe2cefea60
>    </TASK>
> 
> Reported-by: Casey Chen <cachen@purestorage.com>
> Signed-off-by: Keith Busch <kbusch@kernel.org>

Reviewed-by: Ming Lei <ming.lei@redhat.com>


Thanks,
Ming



  parent reply	other threads:[~2025-11-05  1:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-04 22:59 [PATCH] nvme: fix admin request_queue lifetime Keith Busch
2025-11-04 23:08 ` Chaitanya Kulkarni
2025-11-04 23:22   ` Casey Chen
2025-11-05  1:20 ` Ming Lei [this message]
2025-11-05  7:38 ` Hannes Reinecke
2025-11-05 13:14 ` Christoph Hellwig
2025-11-05 20:21 ` Casey Chen
2025-11-05 20:31   ` Keith Busch
2025-11-06  0:10     ` Chaitanya Kulkarni
2025-11-05 21:31 ` Ewan Milne
2025-11-05 22:34   ` Keith Busch
2025-11-06 19:33     ` Ewan Milne
2025-11-30 23:16 ` Sagi Grimberg

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=aQqmX04KSNE-xctU@fedora \
    --to=ming.lei@redhat.com \
    --cc=cachen@purestorage.com \
    --cc=chaitanyak@nvidia.com \
    --cc=hch@lst.de \
    --cc=kbusch@kernel.org \
    --cc=kbusch@meta.com \
    --cc=linux-nvme@lists.infradead.org \
    /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