diff options
author | Ilya Dryomov <idryomov@gmail.com> | 2019-11-08 17:26:51 +0300 |
---|---|---|
committer | Ilya Dryomov <idryomov@gmail.com> | 2019-11-25 13:44:02 +0300 |
commit | b948ad78971fb2c6ed6b53b0edbdd720cfe08d9f (patch) | |
tree | 156192d5d3ce5a560a8c29af39af4e4dd4fe96fd /samples/pidfd | |
parent | 39258aa2db8175271d8079b7685a6e328a8c1a63 (diff) | |
download | linux-b948ad78971fb2c6ed6b53b0edbdd720cfe08d9f.tar.xz |
rbd: treat images mapped read-only seriously
Even though -o ro/-o read_only/--read-only options are very old, we
have never really treated them seriously (on par with snapshots). As
a first step, fail writes to images mapped read-only just like we do
for snapshots.
We need this check in rbd because the block layer basically ignores
read-only setting, see commit a32e236eb93e ("Partially revert "block:
fail op_is_write() requests to read-only partitions"").
Signed-off-by: Ilya Dryomov <idryomov@gmail.com>
Reviewed-by: Jason Dillaman <dillaman@redhat.com>
Reviewed-by: Dongsheng Yang <dongsheng.yang@easystack.cn>
Diffstat (limited to 'samples/pidfd')
0 files changed, 0 insertions, 0 deletions