From: Stefan Hajnoczi <stefanha@gmail.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: Eric Blake <eblake@redhat.com>,
River Chiang <riverchiang@gmail.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Prevent overriding the input file with the output file when using qemu-img
Date: Mon, 29 Jan 2018 13:49:39 +0000 [thread overview]
Message-ID: <20180129134939.GI20446@stefanha-x1.localdomain> (raw)
In-Reply-To: <20180125110208.GB1776@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2156 bytes --]
On Thu, Jan 25, 2018 at 11:02:08AM +0000, Daniel P. Berrangé wrote:
> On Thu, Jan 25, 2018 at 10:52:57AM +0000, Stefan Hajnoczi wrote:
> > On Tue, Jan 23, 2018 at 08:48:15AM -0600, Eric Blake wrote:
> > > On 01/22/2018 10:40 PM, River Chiang wrote:
> > > > Signed-off-by: River Chiang <riverchiang@gmail.com>
> > > >
> > > > ---------------------------------- qemu-img.c
> > > > ----------------------------------
> > > > index 68b375f998..5ce594ea00 100644
> > > > @@ -2098,6 +2098,9 @@ static int img_convert(int argc, char **argv)
> > > > if (s.src_num < 1) {
> > > > error_report("Must specify image file name");
> > > > goto fail_getopt;
> > > > + } else if (!strcmp(argv[optind], out_filename)) {
> > > > + error_report("Override the input file with the output file");
> > > > + goto fail_getopt;
> > >
> > > Comparing names is too prone to false negatives. 'foo' and './foo' are
> > > the same file, but your test won't catch it. Better might be checking
> > > if stat() reports the same dev/inode pair for the two files.
> > >
> > > By the way, your patch is not in proper 'git send-email' format, which
> > > makes it hard to test whether it even applies. More patch submission
> > > hints at http://wiki.qemu.org/Contribute/SubmitAPatch
> >
> > stat(2) cannot be used since the "filenames" may not be a local file,
> > (nbd://, iscsi://, etc).
> >
> > strcmp(3) is also not a full solution, for the reasons you mentioned.
>
> It isn't a full solution, but I does it really need to be ? This check
> is only needed to protect against user accidents. It doesn't trigger
> false reports so won't block valid usage, it merely fails to report
> the problem in some edge cases. IOW, I think strcmp is good enough
> in absence of any other simple solution - better than nothing IMHO.
I don't think a partial solution to protecting the user is worthwhile.
It gives a false impression.
If we do decide to add the strcmp(3) check, then please add it to all
sub-commmands where it's needed. qemu-img dd comes to mind and there
are probably others.
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
prev parent reply other threads:[~2018-01-29 13:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-23 4:40 [Qemu-devel] Prevent overriding the input file with the output file when using qemu-img River Chiang
2018-01-23 14:48 ` Eric Blake
2018-01-23 15:26 ` Eric Blake
2018-01-25 10:52 ` Stefan Hajnoczi
2018-01-25 11:02 ` Daniel P. Berrangé
2018-01-29 13:49 ` Stefan Hajnoczi [this message]
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=20180129134939.GI20446@stefanha-x1.localdomain \
--to=stefanha@gmail.com \
--cc=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=riverchiang@gmail.com \
/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).