From: Hannes Reinecke <hare@suse.de>
To: Christoph Hellwig <hch@lst.de>, Jens Axboe <axboe@kernel.dk>
Cc: Sagi Grimberg <sagi@grimberg.me>,
Mike Snitzer <snitzer@redhat.com>,
Oleksii Kurochko <olkuroch@cisco.com>,
Dongsheng Yang <dongsheng.yang@easystack.cn>,
Ming Lei <ming.lei@redhat.com>,
linux-block@vger.kernel.org, dm-devel@redhat.com,
linux-nvme@lists.infradead.org,
"Martin K . Petersen" <martin.petersen@oracle.com>,
Ilya Dryomov <idryomov@gmail.com>,
ceph-devel@vger.kernel.org
Subject: Re: [dm-devel] [PATCH 2/6] block: remove the NULL bdev check in bdev_read_only
Date: Sun, 10 Jan 2021 15:59:42 +0100 [thread overview]
Message-ID: <9ed48321-4fa9-84a6-ac39-9b4ca56e81e6@suse.de> (raw)
In-Reply-To: <20210109104254.1077093-3-hch@lst.de>
On 1/9/21 11:42 AM, Christoph Hellwig wrote:
> Only a single caller can end up in bdev_read_only, so move the check
> there.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> Reviewed-by: Ming Lei <ming.lei@redhat.com>
> Reviewed-by: Martin K. Petersen <martin.petersen@oracle.com>
> ---
> block/genhd.c | 3 ---
> fs/super.c | 3 ++-
> 2 files changed, 2 insertions(+), 4 deletions(-)
>
Reviewed-by: Hannes Reinecke <hare@suse.de>
Cheers,
Hannes
--
Dr. Hannes Reinecke Kernel Storage Architect
hare@suse.de +49 911 74053 688
SUSE Software Solutions GmbH, Maxfeldstr. 5, 90409 Nürnberg
HRB 36809 (AG Nürnberg), Geschäftsführer: Felix Imendörffer
--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
next prev parent reply other threads:[~2021-01-10 15:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-09 10:42 [dm-devel] split hard read-only vs read-only policy v3 (resend) Christoph Hellwig
2021-01-09 10:42 ` [dm-devel] [PATCH 1/6] dm: use bdev_read_only to check if a device is read-only Christoph Hellwig
2021-01-09 10:42 ` [dm-devel] [PATCH 2/6] block: remove the NULL bdev check in bdev_read_only Christoph Hellwig
2021-01-09 20:14 ` Chaitanya Kulkarni
2021-01-10 14:59 ` Hannes Reinecke [this message]
2021-01-09 10:42 ` [dm-devel] [PATCH 3/6] block: add a hard-readonly flag to struct gendisk Christoph Hellwig
2021-01-09 10:42 ` [dm-devel] [PATCH 4/6] block: propagate BLKROSET on the whole device to all partitions Christoph Hellwig
2021-01-10 15:00 ` Hannes Reinecke
2021-01-09 10:42 ` [dm-devel] [PATCH 5/6] rbd: remove the ->set_read_only method Christoph Hellwig
2021-01-09 10:42 ` [dm-devel] [PATCH 6/6] nvme: allow revalidate to set a namespace read-only Christoph Hellwig
2021-01-09 20:27 ` Chaitanya Kulkarni
2021-01-10 15:01 ` Hannes Reinecke
-- strict thread matches above, loose matches on Subject: below --
2020-12-08 16:28 [dm-devel] split hard read-only vs read-only policy v3 Christoph Hellwig
2020-12-08 16:28 ` [dm-devel] [PATCH 2/6] block: remove the NULL bdev check in bdev_read_only Christoph Hellwig
2020-12-08 16:45 ` Hannes Reinecke
2020-12-07 13:19 [dm-devel] split hard read-only vs read-only policy v2 Christoph Hellwig
2020-12-07 13:19 ` [dm-devel] [PATCH 2/6] block: remove the NULL bdev check in bdev_read_only Christoph Hellwig
2020-12-08 5:23 ` Martin K. Petersen
2020-12-08 10:06 ` Ming Lei
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=9ed48321-4fa9-84a6-ac39-9b4ca56e81e6@suse.de \
--to=hare@suse.de \
--cc=axboe@kernel.dk \
--cc=ceph-devel@vger.kernel.org \
--cc=dm-devel@redhat.com \
--cc=dongsheng.yang@easystack.cn \
--cc=hch@lst.de \
--cc=idryomov@gmail.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=martin.petersen@oracle.com \
--cc=ming.lei@redhat.com \
--cc=olkuroch@cisco.com \
--cc=sagi@grimberg.me \
--cc=snitzer@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;
as well as URLs for NNTP newsgroup(s).