Move PSEUDO_LOCALSTATEDIR outside rootfs
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest1 patch 4 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/1 | runqemu-export-rootfs and friends: don't put pseudo db in target fsmeta/ scripts/ scripts/ | +11 | 4 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/1] Move PSEUDO_LOCALSTATEDIR outside rootfs
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(-)