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

Once the corresponding tarball is available, this should likely be
backported/merged to Jethro and Fido as well.

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.

--Mark

On 2/9/16 1:57 PM, Peter Seebach wrote:
> tarball submitted, but this won't work without it... but you should
> be able to use pseudo_git if you want to see the new shiny.
> 
> Long story short, there has always been a race condition if enough
> clients were trying to simultaneously start a server, but that doesn't
> come up much. But a while back, I added a "feature" where "pseudo <cmd>"
> would try to shut the server down cleanly after running the command,
> which is great for casual command-line use, but meant that we would
> actually hit the race condition.
> 
> Respawn logic drastically reworked, various other changes made to
> make this less likely to come up, and so on.
> 
> Also, pseudo will now abort() if the client can't get a server, which
> could conceivably break things, *but*, it should only be breaking things
> which have in fact been broken all along, we just didn't know it.
> 
> Also a bug fix for cases where mknod is called with only file permission
> bits to create an ordinary file, which GNU tar does if and only if trying
> to extract xattrs apparently (!?!??), and then a followup workaround for
> a problem making ext4 filesystems, where I'm pretty sure the behavior was
> right to begin with but this workaround lets things progress in the mean
> time.
> 
> Whee.
> 
> The following changes since commit d53a0d410ae2390528f1090a131cd3e16d7ebcc5:
> 
>   glibc-locale: fix QA warning (2016-02-07 22:53:22 +0000)
> 
> are available in the git repository at:
> 
>   git://git.yoctoproject.org/poky-contrib seebs/pseudo175
>   http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=seebs/pseudo175
> 
> Peter Seebach (1):
>   pseudo: uprev to 1.7.5
> 
>  meta/recipes-devtools/pseudo/{pseudo_1.7.4.bb => pseudo_1.7.5.bb} | 4 ++--
>  meta/recipes-devtools/pseudo/pseudo_git.bb                        | 4 ++--
>  2 files changed, 4 insertions(+), 4 deletions(-)
>  rename meta/recipes-devtools/pseudo/{pseudo_1.7.4.bb => pseudo_1.7.5.bb} (77%)
> 



  parent reply	other threads:[~2016-02-09 20:11 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 ` Mark Hatle [this message]
2016-02-09 21:16   ` [PATCH 0/1] pseudo 1.7.5 [jethro][fido] Peter Seebach
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=56BA47DD.6020007@windriver.com \
    --to=mark.hatle@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=peter.seebach@windriver.com \
    /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