xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Olaf Hering <olaf@aepfle.de>
Cc: Wei Liu <wei.liu2@citrix.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Ian Campbell <Ian.Campbell@citrix.com>,
	Xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH for-4.5] tools/pygrub: Fix TOCTOU race introduced by c/s 63dcc68
Date: Wed, 29 Oct 2014 18:09:31 +0000	[thread overview]
Message-ID: <54512D5B.1040003@citrix.com> (raw)
In-Reply-To: <20141029160322.GA22428@aepfle.de>

On 29/10/14 16:03, Olaf Hering wrote:
> On Wed, Oct 29, Andrew Cooper wrote:
>
>> In addition, use os.makedirs() which will also create intermediate directories
>> if they don't exist.
> Can this happen in practice, given that /var/run/xen is created by the
> runlevel scripts already? The mkdir is now really just @XEN_RUN_DIR@/pygrub.
>
> Olaf

Yes, although I presume not given the runlevel scripts.

XenServer, and Xapi in particular, is very different from an upstream xl
based system.  It has traditionally had its own initscripts.  We are in
the process of disentangling these, but it is not a trivial amount of work.

The result is that I have positively proved that XenServer hit this race
during automatic testing.  I agree that it shouldn't happen in reality
for a system configured as expected, but that fact alone doesn't
invalidate the fix itself.

~Andrew

  reply	other threads:[~2014-10-29 18:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-29 14:09 [PATCH for-4.5] tools/pygrub: Fix TOCTOU race introduced by c/s 63dcc68 Andrew Cooper
2014-10-29 16:03 ` Olaf Hering
2014-10-29 18:09   ` Andrew Cooper [this message]
2014-10-29 19:43     ` Olaf Hering
2014-11-04 10:48 ` Ian Campbell
2014-11-04 10:52   ` Please *justify* your use of the for-4.5 tag when posting patches Ian Campbell

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=54512D5B.1040003@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=olaf@aepfle.de \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xen.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).