From: Christoph Hellwig <hch@lst.de>
To: Jens Axboe <axboe@kernel.dk>
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>,
Oleksii Kurochko <olkuroch@cisco.com>,
Sagi Grimberg <sagi@grimberg.me>,
Mike Snitzer <snitzer@redhat.com>,
Ilya Dryomov <idryomov@gmail.com>,
Dongsheng Yang <dongsheng.yang@easystack.cn>,
ceph-devel@vger.kernel.org, dm-devel@redhat.com,
linux-block@vger.kernel.org, linux-nvme@lists.infradead.org
Subject: split hard read-only vs read-only policy v3 (resend)
Date: Sat, 9 Jan 2021 11:42:48 +0100 [thread overview]
Message-ID: <20210109104254.1077093-1-hch@lst.de> (raw)
Hi Jens,
this series resurrects a patch from Martin to properly split the flag
indicating a disk has been set read-only by the hardware vs the userspace
policy set through the BLKROSET ioctl.
Note that the last patch only applies to for-next and not to
for-5.11/block. I can hold it back for the first NVMe pull request after
Linus pulled the block tree.
A git tree is available here:
git://git.infradead.org/users/hch/block.git block-hard-ro
Gitweb:
http://git.infradead.org/users/hch/block.git/shortlog/refs/heads/block-hard-ro
Changes since v3:
- rebased to the latest block tree
- indent commit log lines starting with a "#" to make sure git commit
doesn't eat them
Changes since v2:
- fix a few typos
- add a patch to propagate the read-only status from the whole device to
partitions
- add a patch to remove a pointless check from bdev_read_only
Changes since v1:
- don't propagate the policy flag from the whole disk to partitions
- rebased on top of the merge block_device and hd_struct series
next reply other threads:[~2021-01-09 10:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-09 10:42 Christoph Hellwig [this message]
2021-01-09 10:42 ` [PATCH 1/6] dm: use bdev_read_only to check if a device is read-only Christoph Hellwig
2021-01-09 10:42 ` [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
2021-01-09 10:42 ` [PATCH 3/6] block: add a hard-readonly flag to struct gendisk Christoph Hellwig
2021-01-09 10:42 ` [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 ` [PATCH 5/6] rbd: remove the ->set_read_only method Christoph Hellwig
2021-01-09 10:42 ` [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
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=20210109104254.1077093-1-hch@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=ceph-devel@vger.kernel.org \
--cc=dm-devel@redhat.com \
--cc=dongsheng.yang@easystack.cn \
--cc=idryomov@gmail.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=martin.petersen@oracle.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).