From: Peter Seebach <peter.seebach@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/1] pseudo 1.4.4
Date: Tue, 12 Feb 2013 16:52:06 -0600 [thread overview]
Message-ID: <cover.1360709138.git.peter.seebach@windriver.com> (raw)
So, about two days AFTER pseudo 1.4.3 goes in, I finally hit the fairly
obvious bug in the link/linkat() changes. Summary: In general, if parameter
names end in 'path' pseudo tries to do automatic path fixups for them.
This doesn't work well for the *at() functions, because they can need
magic done with their corresponding file descriptors. So linkat() doesn't
take already-converted names.
link(), however, was using fully-expanded names. And when I converted it
to just call linkat(), it preserved this behavior. The obvious failure
is that in a chroot() environment, link() would prepend the chroot path
twice; once in link(), and once in linkat() which it called.
Fixed in pseudo 1.4.4, retested against the test case. Due to the
slightly-too-magical way pseudo works, the only actual changes are to
the names of the parameters of link().
The following changes since commit c58e6cf352774e147038e6543ac95ab0060f2327:
Anders Roxell (1):
distro_check: Remove creation of empty Meego filelist.
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib seebs/pseudo144
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=seebs/pseudo144
Peter Seebach (1):
pseudo_git.bb: Bump to pseudo 1.4.4.
.../pseudo/{pseudo_1.4.3.bb => pseudo_1.4.4.bb} | 4 ++--
meta/recipes-devtools/pseudo/pseudo_git.bb | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
rename meta/recipes-devtools/pseudo/{pseudo_1.4.3.bb => pseudo_1.4.4.bb} (43%)
next reply other threads:[~2013-02-12 23:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-12 22:52 Peter Seebach [this message]
2013-02-12 22:52 ` [PATCH 1/1] pseudo_git.bb: Bump to pseudo 1.4.4 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=cover.1360709138.git.peter.seebach@windriver.com \
--to=peter.seebach@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