qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Cole Robinson <crobinso@redhat.com>, qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qemu-sockets: do not test path with access() before unlinking
Date: Mon, 2 Nov 2015 16:52:16 +0100	[thread overview]
Message-ID: <563786B0.9060300@redhat.com> (raw)
In-Reply-To: <56377EBC.5030402@redhat.com>



On 02/11/2015 16:18, Cole Robinson wrote:
>> > -    if ((access(un.sun_path, F_OK) == 0) &&
>> > -        unlink(un.sun_path) < 0) {
>> > +    if (unlink(un.sun_path) < 0) {
>> >          error_setg_errno(errp, errno,
>> >                           "Failed to unlink socket %s", un.sun_path);
>> >          goto err;
>> > 
> This is a serious semantic change, after this patch you will get:
> 
> $ ./x86_64-softmmu/qemu-system-x86_64 -vnc unix:/tmp/idontexist.sock
> qemu-system-x86_64: -vnc unix:/tmp/idontexist.sock: Failed to start VNC
> server: Failed to unlink socket /tmp/idontexist.sock: No such file or directory
> 
> Previously it would 'just work'. Common libvirt usage depends on this as well
> 
> Yeah there's a TOCTTOU race here, but it's very minor: if sun_path is created
> after the access() check, qemu is just going to fail to start since bind()
> will barf if the unix socket path exists.

You're right.  I misread how to test the change.

The right change is what Markus proposed.

Paolo

      parent reply	other threads:[~2015-11-02 15:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-02 14:10 [Qemu-devel] [PATCH] qemu-sockets: do not test path with access() before unlinking Paolo Bonzini
2015-11-02 15:18 ` Cole Robinson
2015-11-02 15:50   ` Markus Armbruster
2015-11-02 15:52   ` Paolo Bonzini [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=563786B0.9060300@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=crobinso@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@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).