From: Andrew Morton <akpm@linux-foundation.org>
To: Kirill Kuvaldin <kuvkir@epsmu.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Christoph Hellwig <hch@lst.de>, Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: [PATCH] isofs: mounting to regular file may succeed
Date: Tue, 17 Jul 2007 00:04:07 -0700 [thread overview]
Message-ID: <20070717000407.4c854ec8.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070713234721.GG4536@zetta.epsmu.com>
On Sat, 14 Jul 2007 03:47:21 +0400 Kirill Kuvaldin <kuvkir@epsmu.com> wrote:
> 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>
>
> diff --git a/fs/isofs/inode.c b/fs/isofs/inode.c
> index 5c3eecf..ce5062a 100644
> --- a/fs/isofs/inode.c
> +++ b/fs/isofs/inode.c
> @@ -840,6 +840,15 @@ root_found:
> goto out_no_root;
> if (!inode->i_op)
> goto out_bad_root;
> +
> + /* Make sure the root inode is a directory */
> + if (!S_ISDIR(inode->i_mode)) {
> + printk(KERN_WARNING
> + "isofs_fill_super: root inode is not a directory. "
> + "Corrupted media?\n");
> + goto out_iput;
> + }
> +
> /* get the root dentry */
> s->s_root = d_alloc_root(inode);
> if (!(s->s_root))
I don't think any (all?) other filesystems perform checks like this.
Is this something which can/should be performed at the VFS level?
next prev parent reply other threads:[~2007-07-17 7:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-13 23:47 [PATCH] isofs: mounting to regular file may succeed Kirill Kuvaldin
2007-07-14 8:57 ` Kirill Kuvaldin
2007-07-14 19:16 ` Jan Engelhardt
2007-07-15 9:36 ` Kirill Kuvaldin
2007-07-17 7:04 ` Andrew Morton [this message]
2007-07-17 7:08 ` Christoph Hellwig
2007-07-17 7:45 ` Al Viro
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070717000407.4c854ec8.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=hch@lst.de \
--cc=kuvkir@epsmu.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox