Re: [PATCH 5/6] rbd: remove the ->set_read_only method

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: [PATCH 5/6] rbd: remove the ->set_read_only method
From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
Date: Tue, 08 Dec 2020 00:30:17 -0500
Cc: Jens Axboe <axboe@xxxxxxxxx>, Sagi Grimberg <sagi@xxxxxxxxxxx>, Mike Snitzer <snitzer@xxxxxxxxxx>, Oleksii Kurochko <olkuroch@xxxxxxxxx>, Dongsheng Yang <dongsheng.yang@xxxxxxxxxxxx>, linux-block@xxxxxxxxxxxxxxx, dm-devel@xxxxxxxxxx, linux-nvme@xxxxxxxxxxxxxxxxxxx, "Martin K . Petersen" <martin.petersen@xxxxxxxxxx>, Ilya Dryomov <idryomov@xxxxxxxxx>, ceph-devel@xxxxxxxxxxxxxxx
In-reply-to: <20201207131918.2252553-6-hch@lst.de> (Christoph Hellwig's message of "Mon, 7 Dec 2020 14:19:17 +0100")
Organization: Oracle Corporation
References: <20201207131918.2252553-1-hch@lst.de> <20201207131918.2252553-6-hch@lst.de>

Christoph,

> Now that the hardware read-only state can't be changed by the BLKROSET
> ioctl, the code in this method is not required anymore.

Reviewed-by: Martin K. Petersen <martin.petersen@xxxxxxxxxx>

-- 
Martin K. Petersen	Oracle Linux Engineering

--
dm-devel mailing list
dm-devel@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/dm-devel

References:
- split hard read-only vs read-only policy v2
  - From: Christoph Hellwig
- [PATCH 5/6] rbd: remove the ->set_read_only method
  - From: Christoph Hellwig

Prev by Date: Re: [PATCH 6/6] nvme: allow revalidate to set a namespace read-only
Next by Date: Re: [RFC PATCH v2 0/2] add simple copy support
Previous by thread: Re: [PATCH 5/6] rbd: remove the ->set_read_only method
Next by thread: Re: split hard read-only vs read-only policy v2
Index(es):
- Date
- Thread

[Index of Archives] [DM Crypt] [Fedora Desktop] [ATA RAID] [Fedora Marketing] [Fedora Packaging] [Fedora SELinux] [Yosemite Discussion] [KDE Users] [Fedora Docs]

Powered by Linux