From: Kevin Wolf <kwolf@redhat.com>
To: John Snow <jsnow@redhat.com>
Cc: qemu-block@nongnu.org, qemu-devel@nongnu.org,
dgilbert@redhat.com, mreitz@redhat.com
Subject: Re: [Qemu-devel] [PATCH] file-posix: refuse to open directories
Date: Fri, 22 Dec 2017 14:00:18 +0100 [thread overview]
Message-ID: <20171222130018.GE3763@localhost.localdomain> (raw)
In-Reply-To: <20171221224411.8901-1-jsnow@redhat.com>
Am 21.12.2017 um 23:44 hat John Snow geschrieben:
> I don't think there's a legitimate reason to open directories as if
> they were files. This prevents QEMU from opening and attempting to probe
> a directory inode, which can break in exciting ways. One of those ways
> is lseek on ext4/xfs, which will return 0x7fffffffffffffff as the file
> size instead of EISDIR. This can coax QEMU into responding with a
> confusing "file too big" instead of "Hey, that's not a file".
>
> See: https://bugs.launchpad.net/qemu/+bug/1739304/
> Signed-off-by: John Snow <jsnow@redhat.com>
> ---
> block/file-posix.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/block/file-posix.c b/block/file-posix.c
> index 36ee89e940..bd29bdada6 100644
> --- a/block/file-posix.c
> +++ b/block/file-posix.c
> @@ -589,6 +589,11 @@ static int raw_open_common(BlockDriverState *bs, QDict *options,
> s->needs_alignment = true;
> }
> #endif
> + if (S_ISDIR(st.st_mode)) {
> + ret = -EISDIR;
> + error_setg_errno(errp, errno, "Cannot open directory as file");
> + goto fail;
> + }
I think instead of blacklisting directories, the callers should somehow
pass the file types they expect. Which would probably initially be
something like:
file:
S_IFREG: expected
S_IFBLK or S_IFCHR: deprecation warning
else: error
host_device / host_cdrom:
S_IFBLK or S_IFCHR: expected (which one depends on the OS)
else: error
Kevin
next prev parent reply other threads:[~2017-12-22 13:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-21 22:44 [Qemu-devel] [PATCH] file-posix: refuse to open directories John Snow
2017-12-21 22:56 ` no-reply
2017-12-21 23:00 ` John Snow
2017-12-21 23:30 ` Eric Blake
2017-12-22 9:26 ` Daniel P. Berrange
2017-12-22 13:00 ` Kevin Wolf [this message]
2018-01-12 23:30 ` John Snow
2018-01-15 13:23 ` Kevin Wolf
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=20171222130018.GE3763@localhost.localdomain \
--to=kwolf@redhat.com \
--cc=dgilbert@redhat.com \
--cc=jsnow@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).