openembedded-core.lists.openembedded.org archive mirror
 help / color / mirror / Atom feed
From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Alex Kiernan <alex.kiernan@gmail.com>
Cc: Ross Burton <ross@burtonini.com>,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [OE-Core][PATCH 2/2] rootfs-postcommands: Enable rootfs_check_host_user_contaminated
Date: Sun, 21 Jun 2020 17:00:25 +0100	[thread overview]
Message-ID: <964e63ac0bfa723afd2f280b840edcc0340bb442.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAO5Uq5Sb37G8zRNPv=Ue3pxYnVPBgkR=XgHRoWCNs0C9iKuRXA@mail.gmail.com>

On Sun, 2020-06-21 at 16:24 +0100, Alex Kiernan wrote:
> Hi Richard
> 
> On Sat, Jun 20, 2020 at 1:45 PM Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > On Tue, 2020-06-09 at 16:08 +0100, Alex Kiernan wrote:
> > > On Thu, May 21, 2020 at 3:14 PM Alex Kiernan via
> > > lists.openembedded.org <
> > > alex.kiernan=gmail.com@lists.openembedded.org
> > > wrote:
> > > > Hi Ross
> > > > 
> > > > On Thu, Jan 2, 2020 at 11:20 PM Ross Burton <
> > > > ross.burton@intel.com>
> > > > wrote:
> > > > > On 19/12/2019 22:17, Alex Kiernan wrote:
> > > > > > Enable rootfs_check_host_user_contaminated by default
> > > > > 
> > > > > Useful check!
> > > > > 
> > > > > WARNING: Paths in the rootfs are owned by the same user or
> > > > > group
> > > > > as the
> > > > > user running bitbake. See the logfile for the specific paths.
> > > > > 
> > > > > /data/poky-tmp/master/work/intel_corei7_64-poky-linux/core-
> > > > > image-
> > > > > sato/1.0-r0/rootfs/usr/share/fonts/.uuid
> > > > > 
> > > > > /data/poky-tmp/master/work/intel_corei7_64-poky-linux/core-
> > > > > image-
> > > > > sato/1.0-r0/rootfs/usr/share/fonts/ttf/.uuid
> > > > > 
> > > > > (patch incoming)
> > > > > 
> > > > 
> > > > Did you manage to get a patch for this out? I've had a couple
> > > > of
> > > > goes
> > > > at reproducing it and failed, but I suspect I'm not including
> > > > the
> > > > right things. It would be good to get this check enabled early
> > > > in
> > > > the
> > > > release cycle, if we can?
> > > > 
> > > 
> > > Ping?
> > 
> > I'm trying to enable this but its triggering warnings on the
> > autobuilder:
> > 
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/76/builds/2037
> > 
> > Unfortunately the logs are totally useless. I think we'll have to
> > improve the logging before this can be debugged and fixed which
> > blocks
> > this merging.
> > 
> 
> I've had a couple of goes at reproducing this locally, based on the
> configuration I think it's building and can't get it to fail...
> 
> Presumably we need to expose the failure lines from the supplementary
> log file so that they make it into the autobuilder output?

Yes, we need the output to show which files are affected to have some
chance of figuring out how to fix this. The fact its happening
intermittently is somewhat worrying :/.

Cheers,

Richard


  reply	other threads:[~2020-06-21 16:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-19 22:17 [PATCH 1/2] manpages.bbclass: Fix rootfs host corruption Alex Kiernan
2019-12-19 22:17 ` [PATCH 2/2] rootfs-postcommands: Enable rootfs_check_host_user_contaminated Alex Kiernan
2020-01-02 23:20   ` Ross Burton
2020-05-21 14:14     ` [OE-core] [OE-Core][PATCH " Alex Kiernan
     [not found]     ` <161110ADA6F0224D.21901@lists.openembedded.org>
2020-06-09 15:08       ` Alex Kiernan
2020-06-20 12:45         ` Richard Purdie
2020-06-21 15:24           ` Alex Kiernan
2020-06-21 16:00             ` Richard Purdie [this message]
2020-06-22 10:58               ` Alex Kiernan
2020-01-09  2:30 ` [PATCH 1/2] manpages.bbclass: Fix rootfs host corruption Alex Kiernan
2020-01-09 13:36   ` Ross Burton
2020-01-09 14:43     ` Alex Kiernan

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=964e63ac0bfa723afd2f280b840edcc0340bb442.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=alex.kiernan@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross@burtonini.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;
as well as URLs for NNTP newsgroup(s).