Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Keith Busch <kbusch@kernel.org>
To: Maurizio Lombardi <mlombard@redhat.com>
Cc: axboe@kernel.dk, hch@lst.de, sagi@grimberg.me,
	linux-nvme@lists.infradead.org
Subject: Re: [PATCH V2] nvme-pci: fix race condition between reset and nvme_dev_disable()
Date: Thu, 17 Oct 2024 12:08:39 -0600	[thread overview]
Message-ID: <ZxFSp1zDpi7UmLx7@kbusch-mbp.dhcp.thefacebook.com> (raw)
In-Reply-To: <20241015112100.824193-1-mlombard@redhat.com>

On Tue, Oct 15, 2024 at 01:21:00PM +0200, Maurizio Lombardi wrote:
> nvme_dev_disable() modifies the dev->online_queues field, therefore
> nvme_pci_update_nr_queues() should avoid racing against it, otherwise
> we could end up passing invalid values to blk_mq_update_nr_hw_queues().

Thanks, applied to nvme-6.12.


      parent reply	other threads:[~2024-10-17 18:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-15 11:21 [PATCH V2] nvme-pci: fix race condition between reset and nvme_dev_disable() Maurizio Lombardi
2024-10-15 17:27 ` Keith Busch
2024-10-15 17:57   ` Keith Busch
2024-10-17 18:08 ` Keith Busch [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=ZxFSp1zDpi7UmLx7@kbusch-mbp.dhcp.thefacebook.com \
    --to=kbusch@kernel.org \
    --cc=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=linux-nvme@lists.infradead.org \
    --cc=mlombard@redhat.com \
    --cc=sagi@grimberg.me \
    /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