From: Peter Seebach <peter.seebach@windriver.com>
To: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/1] improvements to acl-ptest
Date: Wed, 18 May 2016 16:30:46 -0500 [thread overview]
Message-ID: <cover.1463606862.git.peter.seebach@windriver.com> (raw)
The acl tests assume that umask is 022 (or similar) by default
for some of the permissions tests. The existing run-ptest script
also assumes availability of gpasswd, which we tend to remove by
default, and that the current filesystem supports ACLs. Fix
this by adding a line to the test script for the umask, and making
run-ptest use direct sed to alter /etc/group (it really does need
to) and use a temporary filesystem. (This creates a requirement for
mkfs.ext3, which may be a problem, but it works in our usual
environment, so I figure I'll leave it that way for now?)
The following changes since commit 2fef37fab6967410aff33744c8843bcae028de56:
gcc: Security fix CVE-2016-4490 (2016-05-17 14:42:18 +0100)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib seebs/aclptest
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=seebs/aclptest
Peter Seebach (1):
acl.inc, run-ptest: improve ptest functionality on limited rootfs
meta/recipes-support/attr/acl.inc | 1 +
meta/recipes-support/attr/acl/run-ptest | 67 ++++++++++++++++++--
.../attr/acl/test-fix-directory-permissions.patch | 24 +++++++
3 files changed, 87 insertions(+), 5 deletions(-)
create mode 100644 meta/recipes-support/attr/acl/test-fix-directory-permissions.patch
next reply other threads:[~2016-05-18 21:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 21:30 Peter Seebach [this message]
2016-05-18 21:30 ` [PATCH 1/1] acl.inc, run-ptest: improve ptest functionality on limited rootfs 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.1463606862.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.