public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: william.hauser@meraki.net, openembedded-core@lists.openembedded.org
Cc: William Hauser <whauser@meraki.com>,
	William Hauser <william.hauser@meraki.com>
Subject: Re: [OE-core] [PATCH] package.bbclass: fix image_debugfs symlinks
Date: Sun, 08 Nov 2020 09:29:26 +0000	[thread overview]
Message-ID: <ef018194964950bf6a4a048b7f2134949aba128f.camel@linuxfoundation.org> (raw)
In-Reply-To: <20201104224743.74488-1-whauser@meraki.com>

On Wed, 2020-11-04 at 14:47 -0800, William Hauser via
lists.openembedded.org wrote:
> Allow symlinks to be made in the debugfs by removing an incorrect
> check that
> would always prevent symlinks from being transferred over.
> 
> The comment in this code indicates that the code is meant to ensure
> symlinks
> are only copied to the debugfs if their target has already been
> copied, but
> instead checks for the existence of the symlink that has yet to be
> created.
> As a result this check always fails.
> 
> This check is safe to get rid of since we will only attempt to copy a
> symlink to the debugfs if it's original target exists and is an ELF.
> It
> is, however, still possible for a dead symlink to end up in the
> debugfs
> if its original target was stripped.
> 
> Signed-off-by: William Hauser <william.hauser@meraki.com>
> ---
>  meta/classes/package.bbclass | 8 --------
>  1 file changed, 8 deletions(-)

Unfortunately this patch did show failures in testing:

https://autobuilder.yoctoproject.org/typhoon/#/builders/79/builds/1536

(and the other selftests failed the same way).

oe-selftest -r imagefeatures.ImageFeatures.test_image_gen_debugfs

is how to run that test.

Cheers,

Richard


      reply	other threads:[~2020-11-08  9:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-04 22:47 [PATCH] package.bbclass: fix image_debugfs symlinks William Hauser
2020-11-08  9:29 ` 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=ef018194964950bf6a4a048b7f2134949aba128f.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=whauser@meraki.com \
    --cc=william.hauser@meraki.com \
    --cc=william.hauser@meraki.net \
    /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