From: John Snow <jsnow@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-block@nongnu.org, qemu-devel@nongnu.org,
Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v5] file-posix: specify expected filetypes
Date: Wed, 21 Mar 2018 16:26:06 -0400 [thread overview]
Message-ID: <77891eaa-a0db-981e-ffba-7073143cb23c@redhat.com> (raw)
In-Reply-To: <20180321202501.GJ3898@localhost.localdomain>
On 03/21/2018 04:25 PM, Kevin Wolf wrote:
> Am 21.03.2018 um 21:01 hat John Snow geschrieben:
>> Adjust each caller of raw_open_common to specify if they are expecting
>> host and character devices or not. Tighten expectations of file types upon
>> open in the common code and refuse types that are not expected.
>>
>> This has two effects:
>>
>> (1) Character and block devices are now considered deprecated for the
>> 'file' driver, which expects only S_IFREG, and
>> (2) no file-posix driver (file, host_cdrom, or host_device) can open
>> directories now.
>>
>> 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>
>> ---
>>
>> v5: rebase for 2.12.0-rc0
>>
>> block/file-posix.c | 37 +++++++++++++++++++++++++++++--------
>> qemu-doc.texi | 6 ++++++
>> 2 files changed, 35 insertions(+), 8 deletions(-)
>>
>> diff --git a/block/file-posix.c b/block/file-posix.c
>> index d7fb772c14..31d9afe026 100644
>> --- a/block/file-posix.c
>> +++ b/block/file-posix.c
>> @@ -420,7 +420,8 @@ static QemuOptsList raw_runtime_opts = {
>> };
>>
>> static int raw_open_common(BlockDriverState *bs, QDict *options,
>> - int bdrv_flags, int open_flags, Error **errp)
>> + int bdrv_flags, int open_flags,
>> + bool device, Error **errp)
>> {
>> BDRVRawState *s = bs->opaque;
>> QemuOpts *opts;
>> @@ -558,10 +559,30 @@ static int raw_open_common(BlockDriverState *bs, QDict *options,
>> error_setg_errno(errp, errno, "Could not stat file");
>> goto fail;
>> }
>> - if (S_ISREG(st.st_mode)) {
>> - s->discard_zeroes = true;
>> - s->has_fallocate = true;
>> +
>> + if (!device) {
>> + if (S_ISBLK(st.st_mode)) {
>> + warn_report("Opening a block device as file using 'file' "
>> + "driver is deprecated");
>> + } else if (S_ISCHR(st.st_mode)) {
>> + warn_report("Opening a character device as file using the 'file' "
>> + "driver is deprecated");
>> + } else if (!S_ISREG(st.st_mode)) {
>> + error_setg(errp, "A regular file was expected by the 'file' driver, "
>> + "but something else was given");
>> + goto fail;
>
> ret needs to be set here, otherwise we return success. In my test, I
> still got the wrong message: "Could not refresh total sector count:
> Invalid argument"
>
>> + } else {
>> + s->discard_zeroes = true;
>> + s->has_fallocate = true;
>> + }
>> + } else {
>> + if (!(S_ISCHR(st.st_mode) || S_ISBLK(st.st_mode))) {
>> + error_setg(errp, "host_device/host_cdrom driver expects either "
>> + "a character or block device");
>> + goto fail;
>
> Same here.
>
>> + }
>> }
>
> Do we want a qemu-iotests case for this?
>
> Kevin
>
I'll take the hint :)
--js
next prev parent reply other threads:[~2018-03-21 20:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-21 20:01 [Qemu-devel] [PATCH v5] file-posix: specify expected filetypes John Snow
2018-03-21 20:25 ` Kevin Wolf
2018-03-21 20:26 ` John Snow [this message]
2018-03-21 20:26 ` [Qemu-devel] [PATCH for-2.12 " Eric Blake
2018-03-21 20:36 ` 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=77891eaa-a0db-981e-ffba-7073143cb23c@redhat.com \
--to=jsnow@redhat.com \
--cc=kwolf@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).