aboutsummaryrefslogtreecommitdiffstats
path: root/meta/recipes-devtools/pseudo/pseudo_1.5.1.bb
AgeCommit message (Collapse)Author
2014-07-16pseudo_1.6.0.bb: uprev to pseudo 1.6Peter Seebach
This uprevs pseudo to 1.6. This merges in all of the existing fixes, and also adds partial support for extended attributes, including storing arbitrary extended attributes in the database, and also interpreting the posix permissions ACLs as chmod requests. The extended attribute support means we need xattr.h, the simplest way to be sure of this is to build attr before pseudo, which doesn't take long. Signed-off-by: Peter Seebach <peter.seebach@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-05-23pseudo: handle fchmodat better, mask out unwanted write bitsPeter Seebach
It turns out that pseudo's decision not to report errors from the host system's fchmodat() can break GNU tar in a very strange way, resulting in directories being mode 0700 instead of whatever they should have been. Additionally, it turns out that if you make directories in your rootfs mode 777, that results in the local copies being mode 777, which could allow a hypothetical attacker with access to the machine to add files to your rootfs image. We should mask out the 022 bits when making actual mode changes in the rootfs. This patch represents a backport to the 1.5.1 branch of three patches from the 1.6 branch, because it took a couple of tries to get this quite right. Signed-off-by: Peter Seebach <peter.seebach@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2014-03-31pseudo-1.5.1: keep install command directory modeyanjun.zhu
When install command sets the created directory mode, pseudo will change the mode of the directory to 0700 incorrectly. Backport patch to fix it. Signed-off-by: yanjun.zhu <yanjun.zhu@windriver.com> Signed-off-by: Kai Kang <kai.kang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-09-30pseudo: Fix race problemsRichard Purdie
There is a potential issue with the fastop code in pseudo since a process may exit and allow some other function to run before the server has processed the commands run by the process. Issues have been see with unpredictable file permissions. To avoid this, we ping the server before exitting which guarantees it has processed the current command queue. The patch was written by peter.seebach@windriver.com [YOCTO #5132] Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-09-06pseudo: fix memory leak and missed privilege dropPeter A. Bigot
qemu.bbclass adds PSEUDO_UNLOAD=1 in qemu_run_binary to avoid reference to pseudo functions that may not exist in the target environment. This patch detects the addition of that variable within the environment to which the call applies, even if not present in the parent environment. As a side effect it fixes a memory leak. [YOCTO #4843] Signed-off-by: Peter A. Bigot <pab@pabigot.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-03-01Update pseudo to 1.5.1Peter Seebach
pseudo 1.5's enable-force-async works great, unless you use a host where, inexplicably, stat(2) reports inconsistent and changing values for a file's size or times for some time unless a file has been fsynced, in which case you might want a way to cause an fsync to work. Also noticed that some recent changes never made it into the docs, so I did a little cleanup there. And changed the way NDEBUG suppresses pseudo's debug messages, so arguments to them with possible side effects (like calls into functions in another translation unit) can be omitted, which should drastically reduce computational time if anyone ever uses NDEBUG. Signed-off-by: Peter Seebach <peter.seebach@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>