summaryrefslogtreecommitdiffstats
path: root/include
diff options
context:
space:
mode:
authorKirill Kuvaldin <kuvkir@epsmu.com>2007-07-31 09:38:58 +0200
committerLinus Torvalds <torvalds@woody.linux-foundation.org>2007-08-01 00:39:41 +0200
commit817794e0df5fea495396c18878804044436832be (patch)
tree2560d16e6299eb8879fc821b2e5d36ee5631eb54 /include
parentremove tx3912fb (diff)
downloadlinux-817794e0df5fea495396c18878804044436832be.tar.xz
linux-817794e0df5fea495396c18878804044436832be.zip
isofs: mounting to regular file may succeed
It turned out that mounting a corrupted ISO image to a regular file may succeed, e.g. if an image was prepared as follows: $ dd if=correct.iso of=bad.iso bs=4k count=8 We then can mount it to a regular file: # mount -o loop -t iso9660 bad.iso /tmp/file But mounting it to a directory fails with -ENOTDIR, simply because the root directory inode doesn't have S_IFDIR set and the condition in graft_tree() is met: if (S_ISDIR(nd->dentry->d_inode->i_mode) != S_ISDIR(mnt->mnt_root->d_inode->i_mode)) return -ENOTDIR This is because the root directory inode was read from an incorrect block. It's supposed to be read from sbi->s_firstdatazone, which is an absolute value and gets messed up in the case of an incorrect image. In order to somehow circumvent this we have to check that the root directory inode is actually a directory after all. Signed-off-by: Kirill Kuvaldin <kuvkir@epsmu.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions