Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Alex Franco <alejandro.franco@linux.intel.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
	Christopher Larson <clarson@kergoth.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>,
	openembedded-commits@lists.openembedded.org
Subject: Re: [oe-commits] Alex Franco : Fix mode +st on TMPDIR when creating it
Date: Wed, 2 Sep 2015 11:37:43 -0500	[thread overview]
Message-ID: <55E725D7.3@linux.intel.com> (raw)
In-Reply-To: <1441192499.24871.51.camel@linuxfoundation.org>

Thanks, I have sent a patch after removing the -R and testing a bit

Alex Franco

On 09/02/2015 06:14 AM, Richard Purdie wrote:
> On Tue, 2015-09-01 at 16:47 -0700, Christopher Larson wrote:
>> On Tue, Sep 1, 2015 at 4:11 PM, Alex Franco
>> <alejandro.franco@linux.intel.com> wrote:
>>          I gather the original reason (for the sanity test, as well as
>>          these changes) is that it is better for everything under
>>          BUILDDIR - and certainly TMPDIR to be owned by the user
>>          running bitbake and have standard permissions, the sticky bit
>>          itself would prevent a user running bitbake, even with +rwx
>>          permissions, from making changes to items it might need to
>>          manipulate, if those are not owned by this user. Similarly
>>          setuid and setgid might propagate user/group ownerships
>>          different from the user bitbake is running as, into BUILDDIR
>>          and TMPDIR (and items therein).
>>          
>>          For more info take a look at:
>>          https://bugzilla.yoctoproject.org/show_bug.cgi?id=7669
>>          
>>          Perhaps there are more pressing reasons, perhaps Christopher
>>          Larson can comment a bit on this.
>>
>> Indeed, the g+s can flow down into the files put into the packages,
>> and then into the rootfs. I ran into a this problem quite a bit, since
>> my project areas are in a g+s area to keep the files accessible to the
>> group.
>
> There is actually another problem here. The -R means if you do this to
> an existing build directory, it takes around 10 mins on the machine I
> just rebooted with a cold cache. We need to lose the -R there.
>
> Cheers,
>
> Richard
>
>



  reply	other threads:[~2015-09-02 16:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20150901104522.9FC59505A9@opal.openembedded.org>
2015-09-01 19:09 ` [oe-commits] Alex Franco : Fix mode +st on TMPDIR when creating it Martin Jansa
2015-09-01 23:11   ` Alex Franco
2015-09-01 23:47     ` Christopher Larson
2015-09-02 11:14       ` Richard Purdie
2015-09-02 16:37         ` Alex Franco [this message]
2015-09-03 11:59   ` Richard Purdie

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=55E725D7.3@linux.intel.com \
    --to=alejandro.franco@linux.intel.com \
    --cc=clarson@kergoth.com \
    --cc=openembedded-commits@lists.openembedded.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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