summaryrefslogtreecommitdiffstats
path: root/fs/nilfs2
diff options
context:
space:
mode:
authorChuck Ebbert <cebbert@redhat.com>2011-02-16 18:11:53 -0500
committerLinus Torvalds <torvalds@linux-foundation.org>2011-02-16 16:48:13 -0800
commite51900f7d38cbcfb481d84567fd92540e7e1d23a (patch)
treef732388a0efab2967fddc0afd0f2200731e34d02 /fs/nilfs2
parenta2640111d5edb3f4e6dd6089c0dbddc7590110b4 (diff)
downloadtalos-op-linux-e51900f7d38cbcfb481d84567fd92540e7e1d23a.tar.gz
talos-op-linux-e51900f7d38cbcfb481d84567fd92540e7e1d23a.zip
block: revert block_dev read-only check
This reverts commit 75f1dc0d076d ("block: check bdev_read_only() from blkdev_get()"). That commit added stricter checking to make sure devices that were being used read-only were actually opened in that mode. It turns out that the change breaks a bunch of kernel code that opens block devices. Affected systems include dm, md, and the loop device. Because strict checking for read-only opens of block devices was not done before this, the code that opens the devices was opening them read-write even if they were being used read-only. Auditing all that code will take time, and new userspace packages for dm, mdadm, etc. will also be required. Signed-off-by: Chuck Ebbert <cebbert@redhat.com> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'fs/nilfs2')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud