From: Michael Tokarev <mjt@tls.msk.ru>
To: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, eblake@redhat.com, armbru@redhat.com,
crobinso@redhat.com
Subject: Re: [Qemu-trivial] [PATCH v2] qemu-sockets: do not test path with access() before unlinking
Date: Fri, 06 Nov 2015 11:05:57 +0300 [thread overview]
Message-ID: <563C5F65.6020807@msgid.tls.msk.ru> (raw)
In-Reply-To: <1446644927-8764-1-git-send-email-pbonzini@redhat.com>
04.11.2015 16:48, 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.
Applied to -trivial, thanks!
/mjt
WARNING: multiple messages have this Message-ID (diff)
From: Michael Tokarev <mjt@tls.msk.ru>
To: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, armbru@redhat.com, crobinso@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2] qemu-sockets: do not test path with access() before unlinking
Date: Fri, 06 Nov 2015 11:05:57 +0300 [thread overview]
Message-ID: <563C5F65.6020807@msgid.tls.msk.ru> (raw)
In-Reply-To: <1446644927-8764-1-git-send-email-pbonzini@redhat.com>
04.11.2015 16:48, 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.
Applied to -trivial, thanks!
/mjt
next prev parent reply other threads:[~2015-11-06 8:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-04 13:48 [Qemu-trivial] [PATCH v2] qemu-sockets: do not test path with access() before unlinking Paolo Bonzini
2015-11-04 13:48 ` [Qemu-devel] " Paolo Bonzini
2015-11-04 14:08 ` [Qemu-trivial] " Markus Armbruster
2015-11-04 14:08 ` Markus Armbruster
2015-11-04 14:15 ` [Qemu-trivial] " Edgar E. Iglesias
2015-11-04 14:15 ` Edgar E. Iglesias
2015-11-06 8:05 ` Michael Tokarev [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=563C5F65.6020807@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=armbru@redhat.com \
--cc=crobinso@redhat.com \
--cc=eblake@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.