Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Peter Seebach <peter.seebach@windriver.com>
To: Mark Hatle <mark.hatle@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/1] pseudo 1.7.5 [jethro][fido]
Date: Tue, 9 Feb 2016 15:16:35 -0600	[thread overview]
Message-ID: <20160209151635.6327ebb0@seebs-worktop> (raw)
In-Reply-To: <56BA47DD.6020007@windriver.com>

On Tue, 9 Feb 2016 14:11:09 -0600
Mark Hatle <mark.hatle@windriver.com> wrote:

> Everything remains compatible, but it does fix a subtle race condition that can
> lead to files under pseudo control inheriting their host system permissions.
> 
> See bug 9031 for more details.

For reference, the thing which exposed the circumstance where this was
actually remotely likely to come up was added in f1d4744, back in 2014,
and somehow the actual change isn't mentioned in ChangeLog.txt, but in
practice it's been there since 1.6.1. But it would only (probably) show
up if you ran some commands with "pseudo <cmd>" *while* running other
things using a pseudo server normally.

-s
-- 
Listen, get this.  Nobody with a good compiler needs to be justified.


  reply	other threads:[~2016-02-09 21:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-09 19:57 [PATCH 0/1] pseudo 1.7.5 Peter Seebach
2016-02-09 19:57 ` [PATCH 1/1] pseudo: uprev to 1.7.5 Peter Seebach
2016-02-09 20:11 ` [PATCH 0/1] pseudo 1.7.5 [jethro][fido] Mark Hatle
2016-02-09 21:16   ` Peter Seebach [this message]
2016-02-09 21:30     ` Richard Purdie
2016-02-09 21:52   ` Andreas Müller
2016-02-10  0:25     ` Mark Hatle
2016-02-10 23:21     ` Peter Seebach

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=20160209151635.6327ebb0@seebs-worktop \
    --to=peter.seebach@windriver.com \
    --cc=mark.hatle@windriver.com \
    --cc=openembedded-core@lists.openembedded.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