From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Khem Raj <raj.khem@gmail.com>, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH V2 3/3] dbus-test: Replace cp -a/-r with portable options
Date: Tue, 10 Mar 2020 08:32:52 +0000 [thread overview]
Message-ID: <9ed228f70b3728e140aa5a539bab07759d6d9914.camel@linuxfoundation.org> (raw)
In-Reply-To: <20200310011544.3022342-3-raj.khem@gmail.com>
On Mon, 2020-03-09 at 18:15 -0700, Khem Raj wrote:
> -r are not posix defined and -a leaks UID of
> build user into target
>
> Errors like below are fixed when -a is used
>
> bus/connection.h is owned by uid 1000, which is the same as t
> he user running bitbake. This may be due to host contamination
>
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> ---
> v2: Improve commit message for clear reason for change
>
> meta/recipes-core/dbus/dbus-test_1.12.16.bb | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/meta/recipes-core/dbus/dbus-test_1.12.16.bb b/meta/recipes-core/dbus/dbus-test_1.12.16.bb
> index bea0e74ed0..91e2ba69d2 100644
> --- a/meta/recipes-core/dbus/dbus-test_1.12.16.bb
> +++ b/meta/recipes-core/dbus/dbus-test_1.12.16.bb
> @@ -70,11 +70,11 @@ do_install_ptest() {
>
> install ${B}/test/test-segfault ${D}${PTEST_PATH}/test
>
> - cp -r ${B}/test/data ${D}${PTEST_PATH}/test
> + cp -R --no-dereference --preserve=mode,links ${B}/test/data ${D}${PTEST_PATH}/test
> install ${B}/dbus/.libs/test-dbus ${D}${PTEST_PATH}/test
>
> install -d ${D}${PTEST_PATH}/test/.libs
> - cp -a ${B}/dbus/.libs/*.so* ${D}${PTEST_PATH}/test/.libs
> + cp -R --no-dereference --preserve=mode,links ${B}/dbus/.libs/*.so* ${D}${PTEST_PATH}/test/.libs
>
> # Remove build host references...
> find "${D}${PTEST_PATH}/test/data" \( -name *.service -o -name *.conf -o -name "*.aaprofile" \) -type f -exec \
I still want to understand why only you are seeing this first.
The implication is that we have to change most uses of "cp -r" for "cp -R --no-dereference --preserve=mode,links
" in OE-Core and every other OE layer.
If we have to do that, fine, but I do want to understand what set of
circumstances triggers the issue first.
Cheers,
Richard
prev parent reply other threads:[~2020-03-10 8:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-10 1:15 [PATCH V2 1/3] ruby: Use arm32 for coroutines on 32bit-arm Khem Raj
2020-03-10 1:15 ` [PATCH V2 2/3] valgrind: Fix timerfd syscall test to be 64bit time_t safe Khem Raj
2020-03-10 1:15 ` [PATCH V2 3/3] dbus-test: Replace cp -a/-r with portable options Khem Raj
2020-03-10 8:32 ` Richard Purdie [this message]
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=9ed228f70b3728e140aa5a539bab07759d6d9914.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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