summaryrefslogtreecommitdiff
path: root/fs/fscache/Kconfig
diff options
context:
space:
mode:
authorJan Kara <jack@suse.cz>2013-07-25 11:49:11 +0200
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2013-09-26 17:18:28 -0700
commit4b5fe51a9a8e6d4c74a6f2717bf25e4132c551d3 (patch)
treeeac45eba4b1629528a78dd7daa0900ca330c87a8 /fs/fscache/Kconfig
parent1ca91545961a92067cb8ad3ebc1558c8d1574456 (diff)
isofs: Refuse RW mount of the filesystem instead of making it RO
commit 17b7f7cf58926844e1dd40f5eb5348d481deca6a upstream. Refuse RW mount of isofs filesystem. So far we just silently changed it to RO mount but when the media is writeable, block layer won't notice this change and thus will think device is used RW and will block eject button of the drive. That is unexpected by users because for non-writeable media eject button works just fine. Userspace mount(8) command handles this just fine and retries mounting with MS_RDONLY set so userspace shouldn't see any regression. Plus any tool mounting isofs is likely confronted with the case of read-only media where block layer already refuses to mount the filesystem without MS_RDONLY set so our behavior shouldn't be anything new for it. Reported-by: Hui Wang <hui.wang@canonical.com> Signed-off-by: Jan Kara <jack@suse.cz> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'fs/fscache/Kconfig')
0 files changed, 0 insertions, 0 deletions