From: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-trivial@nongnu.org, crobinso@redhat.com,
qemu-devel@nongnu.org, armbru@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2] qemu-sockets: do not test path with access() before unlinking
Date: Wed, 4 Nov 2015 15:15:46 +0100 [thread overview]
Message-ID: <20151104141546.GC20036@toto> (raw)
In-Reply-To: <1446644927-8764-1-git-send-email-pbonzini@redhat.com>
On Wed, Nov 04, 2015 at 02:48:47PM +0100, Paolo Bonzini wrote:
> Using access() is a time-of-check/time-of-use race condition. It is
> okay to use them to provide better error messages, but that is pretty
> much it.
>
> This is not one such case; on the other hand, access() *will* skip
> unlink() for a non-existent path, so ignore ENOENT return values from
> the unlink() system call.
>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Reviewed-by: Edgar E. Iglesias <edgar.iglesias@xilinx.com>
> ---
> util/qemu-sockets.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/util/qemu-sockets.c b/util/qemu-sockets.c
> index 9142917..de9145a 100644
> --- a/util/qemu-sockets.c
> +++ b/util/qemu-sockets.c
> @@ -751,8 +751,7 @@ int unix_listen_opts(QemuOpts *opts, Error **errp)
> qemu_opt_set(opts, "path", un.sun_path, &error_abort);
> }
>
> - if ((access(un.sun_path, F_OK) == 0) &&
> - unlink(un.sun_path) < 0) {
> + if (unlink(un.sun_path) < 0 && errno != ENOENT) {
> error_setg_errno(errp, errno,
> "Failed to unlink socket %s", un.sun_path);
> goto err;
> --
> 2.5.0
>
>
next prev parent reply other threads:[~2015-11-04 14:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-04 13:48 [Qemu-devel] [PATCH v2] qemu-sockets: do not test path with access() before unlinking Paolo Bonzini
2015-11-04 14:08 ` Markus Armbruster
2015-11-04 14:15 ` Edgar E. Iglesias [this message]
2015-11-06 8:05 ` Michael Tokarev
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=20151104141546.GC20036@toto \
--to=edgar.iglesias@gmail.com \
--cc=armbru@redhat.com \
--cc=crobinso@redhat.com \
--cc=pbonzini@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).