diff options
| author | Ilya Dryomov <idryomov@gmail.com> | 2019-05-03 17:27:03 +0200 |
|---|---|---|
| committer | Ilya Dryomov <idryomov@gmail.com> | 2019-05-07 19:43:04 +0200 |
| commit | b91a7bdca4439e286f26cdd6c15ed338e6a9fda2 (patch) | |
| tree | 42d2f711a43e483b30a68dac8e23bac1af3a94a9 /net/vmw_vsock | |
| parent | a32e414325c2f0d430436e4708a33c756b082fd8 (diff) | |
| download | linux-stable-b91a7bdca4439e286f26cdd6c15ed338e6a9fda2.tar.gz linux-stable-b91a7bdca4439e286f26cdd6c15ed338e6a9fda2.tar.bz2 linux-stable-b91a7bdca4439e286f26cdd6c15ed338e6a9fda2.zip | |
rbd: don't assert on writes to snapshots
The check added in commit 721c7fc701c7 ("block: fail op_is_write()
requests to read-only partitions") was lifted in commit a32e236eb93e
("Partially revert "block: fail op_is_write() requests to read-only
partitions""). Basic things like user triggered writes and discards
are still caught, but internal kernel users can submit anything. In
particular, ext4 will attempt to write to the superblock if it detects
errors in the filesystem, even if the filesystem is mounted read-only
on a read-only partition.
The assert is overkill regardless.
Signed-off-by: Ilya Dryomov <idryomov@gmail.com>
Diffstat (limited to 'net/vmw_vsock')
0 files changed, 0 insertions, 0 deletions