From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@lst.de>
Cc: Justin Sanders <justin@coraid.com>,
Josef Bacik <josef@toxicpanda.com>,
Xianting Tian <xianting_tian@126.com>,
linux-block@vger.kernel.org, dm-devel@redhat.com,
Stefan Haberland <sth@linux.ibm.com>,
Jan Hoeppner <hoeppner@linux.ibm.com>,
linux-kernel@vger.kernel.org, nbd@other.debian.org,
linux-nvme@lists.infradead.org, linux-s390@vger.kernel.org
Subject: Re: fix block device size update serialization v2
Date: Sat, 29 Aug 2020 10:47:11 -0600 [thread overview]
Message-ID: <b1960016-c265-1e1d-cfd7-de2330bc5eac@kernel.dk> (raw)
In-Reply-To: <20200827074758.GA8009@lst.de>
On 8/27/20 1:47 AM, Christoph Hellwig wrote:
> Jens, can you consider this for 5.9? It reliably fixes the reported
> hangs with nvme hotremoval that we've had for a few releases.
I've queued this up for 5.10. I think it's too late for 5.9 at this
point, and it's not a regression in this release.
--
Jens Axboe
prev parent reply other threads:[~2020-08-29 16:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-23 9:10 fix block device size update serialization v2 Christoph Hellwig
2020-08-23 9:10 ` [PATCH 1/3] block: replace bd_set_size with bd_set_nr_sectors Christoph Hellwig
2020-08-24 8:25 ` Sagi Grimberg
2020-08-23 9:10 ` [PATCH 2/3] block: fix locking for struct block_device size updates Christoph Hellwig
2020-08-24 7:36 ` Hannes Reinecke
2020-08-24 8:26 ` Sagi Grimberg
2020-08-23 9:10 ` [PATCH 3/3] nvme: don't call revalidate_disk from nvme_set_queue_dying Christoph Hellwig
2020-08-24 7:37 ` Hannes Reinecke
2020-08-24 8:26 ` Sagi Grimberg
2020-08-27 7:47 ` fix block device size update serialization v2 Christoph Hellwig
2020-08-29 16:47 ` 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=b1960016-c265-1e1d-cfd7-de2330bc5eac@kernel.dk \
--to=axboe@kernel.dk \
--cc=dm-devel@redhat.com \
--cc=hch@lst.de \
--cc=hoeppner@linux.ibm.com \
--cc=josef@toxicpanda.com \
--cc=justin@coraid.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-s390@vger.kernel.org \
--cc=nbd@other.debian.org \
--cc=sth@linux.ibm.com \
--cc=xianting_tian@126.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