aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/block/cryptoloop.c
diff options
context:
space:
mode:
authorIlya Dryomov <idryomov@gmail.com>2019-11-12 19:41:48 +0100
committerIlya Dryomov <idryomov@gmail.com>2019-11-25 11:44:03 +0100
commit3fe69921dbb29e7335e5c244d1ef66efd154f84b (patch)
tree876e65a83f3ef657f46a86ab0d751d9904df3395 /drivers/block/cryptoloop.c
parentrbd: disallow read-write partitions on images mapped read-only (diff)
downloadlinux-dev-3fe69921dbb29e7335e5c244d1ef66efd154f84b.tar.xz
linux-dev-3fe69921dbb29e7335e5c244d1ef66efd154f84b.zip
rbd: don't acquire exclusive lock for read-only mappings
A read-only mapping should be usable with read-only OSD caps, so neither the header lock nor the object map lock can be acquired. Unfortunately, this means that images mapped read-only lose the advantage of the object map. Snapshots, however, can take advantage of the object map without any exclusionary locks, so if the object map is desired, snapshot the image and map the snapshot instead of the image. 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 'drivers/block/cryptoloop.c')
0 files changed, 0 insertions, 0 deletions