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: hare@suse.de, hch@lst.de, dwagner@suse.de,
	linux-nvme@lists.infradead.org, mlombard@arkamax.eu
Subject: Re: [PATCH V2] nvmet: fix max_qid race between configfs and controller allocation
Date: Thu, 13 Aug 2026 10:25:54 -0600	[thread overview]
Message-ID: <an3wEhqGJ59tiynL@kbusch-mbp> (raw)
In-Reply-To: <20260813131850.79899-1-mlombard@redhat.com>

On Thu, Aug 13, 2026 at 03:18:50PM +0200, Maurizio Lombardi wrote:
> The function nvmet_subsys_attr_qid_max_store() can race against
> nvmet_alloc_ctrl() when a subsystem's max_qid limit is modified.

Thanks, applied to nvme-7.3.


      reply	other threads:[~2026-08-13 16:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-13 13:18 [PATCH V2] nvmet: fix max_qid race between configfs and controller allocation Maurizio Lombardi
2026-08-13 16:25 ` 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=an3wEhqGJ59tiynL@kbusch-mbp \
    --to=kbusch@kernel.org \
    --cc=dwagner@suse.de \
    --cc=hare@suse.de \
    --cc=hch@lst.de \
    --cc=linux-nvme@lists.infradead.org \
    --cc=mlombard@arkamax.eu \
    --cc=mlombard@redhat.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