aboutsummaryrefslogtreecommitdiffstats
path: root/fs/fuse
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 16:52:48 -0700
commitcd76cc4459ac83aa17226ceac9058abbfe8385c8 (patch)
treebc400e585f3522377815b75ab600b9a87d78abe5 /fs/fuse
parent85a39b77027438bec7f1a1ebbbc46925d22f7b5c (diff)
downloadkernel_samsung_smdk4412-cd76cc4459ac83aa17226ceac9058abbfe8385c8.zip
kernel_samsung_smdk4412-cd76cc4459ac83aa17226ceac9058abbfe8385c8.tar.gz
kernel_samsung_smdk4412-cd76cc4459ac83aa17226ceac9058abbfe8385c8.tar.bz2
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/fuse')
0 files changed, 0 insertions, 0 deletions