linux-nvme.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@lst.de>, martin.petersen@oracle.com
Cc: Lihong Kou <koulihong@huawei.com>,
	kbusch@kernel.org, sagi@grimberg.me, linux-block@vger.kernel.org,
	linux-nvme@lists.infradead.org
Subject: Re: fix an integrity profile unregistration race
Date: Tue, 14 Sep 2021 20:03:52 -0600	[thread overview]
Message-ID: <fe10467b-e45a-7c2e-433c-f52ef9b02e09@kernel.dk> (raw)
In-Reply-To: <20210914070657.87677-1-hch@lst.de>

On 9/14/21 1:06 AM, Christoph Hellwig wrote:
> Hi all,
> 
> this series fixes a race when the integrity profile is unregistered on a
> live gendisk.  This is a slight twist on a patch sent by Lihong, which
> I've taken over as she is out on vacation for the next two weeks.

Applied, thanks.

-- 
Jens Axboe


_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme

      parent reply	other threads:[~2021-09-15  2:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-14  7:06 fix an integrity profile unregistration race Christoph Hellwig
2021-09-14  7:06 ` [PATCH 1/3] block: check if a profile is actually registered in blk_integrity_unregister Christoph Hellwig
2021-09-14  7:10   ` Sagi Grimberg
2021-09-14  7:06 ` [PATCH 2/3] block: flush the integrity workqueue " Christoph Hellwig
2021-09-14  7:19   ` Sagi Grimberg
2021-09-14  7:06 ` [PATCH 3/3] nvme: remove the call to nvme_update_disk_info in nvme_ns_remove Christoph Hellwig
2021-09-14  7:19   ` Sagi Grimberg
2021-09-15  2:03 ` Jens Axboe [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=fe10467b-e45a-7c2e-433c-f52ef9b02e09@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=kbusch@kernel.org \
    --cc=koulihong@huawei.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=martin.petersen@oracle.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;
as well as URLs for NNTP newsgroup(s).