mirror of https://github.com/ceph/ceph
d72fca26ed
Since kernel 5.12, hardware read-only state and user read-only policy (BLKROGET/SET ioctls) are tracked separately in the block layer. As the purpose of our ->set_read_only() method was exactly that, it was removed. As a side effect, BLKROSET no longer returns EROFS on an attempt to make a read-only mapping read-write with "blockdev --setrw". The policy gets updated, but the device remains read-only as before because the hardware (== mapping) state is controlled by the driver. Fixes: https://tracker.ceph.com/issues/49858 Signed-off-by: Ilya Dryomov <idryomov@gmail.com> |
||
|---|---|---|
| .. | ||
| common.sh | ||
| krbd_blkroset.t | ||
| krbd_deep_flatten.t | ||
| krbd_discard.t | ||
| krbd_discard_4M.t | ||
| krbd_discard_512b.t | ||
| krbd_discard_granularity.t | ||
| krbd_get_features.t | ||
| krbd_huge_image.t | ||
| krbd_modprobe.t | ||
| krbd_msgr_segments.t | ||
| krbd_parent_overlap.t | ||
| krbd_whole_object_zeroout.t | ||
| krbd_zeroout.t | ||
| rbd.sh | ||