From: Peter Seebach <peter.seebach@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/1] Move PSEUDO_LOCALSTATEDIR outside rootfs
Date: Tue, 21 Aug 2012 13:31:51 -0500 [thread overview]
Message-ID: <cover.1345573717.git.peter.seebach@windriver.com> (raw)
There's a race condition in one of our (non-poky) builds which involves
a rootfs getting deleted while a pseudo process has a db in it open.
This caused me to realize that there existed a pseudo database in a
target filesystem, which made me panic. And we have a few really strange
reports I've never been able to reproduce where target filesystems
under qemu went pear-shaped in ways that look like pseudo suddenly
got really, really, confused.
Like say what would happen if a target could wipe out its own filesystem
permissions, because they were in its rootfs. :P
I haven't tested this super thoroughly, but I can still complete builds
and SDK builds with it, and it makes sense.
The following changes since commit 4ef8960c8d2876914bb78cbdce5fae3c5297e942:
Khem Raj (1):
gcc-cross-intermediate, gcc-crosssdk-intermediate: Remove
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib seebs/varpseudo
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=seebs/varpseudo
Peter Seebach (1):
runqemu-export-rootfs and friends: don't put pseudo db in target fs
.../installer/adt-installer/scripts/extract_rootfs | 7 +++----
scripts/runqemu-export-rootfs | 2 +-
scripts/runqemu-extract-sdk | 13 +++++++------
3 files changed, 11 insertions(+), 11 deletions(-)
next reply other threads:[~2012-08-21 18:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-21 18:31 Peter Seebach [this message]
2012-08-21 18:31 ` [PATCH 1/1] runqemu-export-rootfs and friends: don't put pseudo db in target fs Peter Seebach
2012-08-22 16:34 ` Scott Garman
2012-08-22 19:20 ` Peter Seebach
2012-08-22 19:39 ` Richard Purdie
2012-08-27 16:17 ` 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.1345573717.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