All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/linux-tools: Exclude checking PE binaries from perf test
Date: Wed, 28 Sep 2022 23:38:56 +0200	[thread overview]
Message-ID: <20220928233856.77bb191c@windsurf> (raw)
In-Reply-To: <20220927221133.594071-1-f.fainelli@gmail.com>

Hello Florian,

On Tue, 27 Sep 2022 15:11:33 -0700
Florian Fainelli <f.fainelli@gmail.com> wrote:

> Since upstream Linux commit ed21d6d7c48e6e96c2d617e304a7ebfbd17b1807
> ("perf tests: Add test for PE binary format support") present in >=
> v5.10 there is an unconditional installation of PE binaries which will
> be rejected by the check-bin-arch script.
> 
> Make sure that these binaries are excluded from being checked to allow
> the installation of the perf tests.
> 
> Fixes: 6fcdaa4c5096 ("package/linux-tools: Allow installation of perf scripts")
> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>

Thanks for the patch! Before merging it, I'd like to understand a
little bit more how readelf behaves for these PE files. Indeed in
check-bin-arch, we are doing:

        arch=$(LC_ALL=C ${readelf} -h "${TARGET_DIR}/${f}" 2>&1 | \
                       sed -r -e '/^  Machine: +(.+)/!d; s//\1/;' | head -1)

        # If no architecture found, assume it was not an ELF file
        if test "${arch}" = "" ; then
                continue
        fi

for a PE file, I would expect readelf to badly fail, and therefore
${arch} to be empty, and the file simply ignored.

What is the behavior/output of readelf on these PE files?

Thanks!

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2022-09-28 21:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-27 22:11 [Buildroot] [PATCH] package/linux-tools: Exclude checking PE binaries from perf test Florian Fainelli
2022-09-28 21:38 ` Thomas Petazzoni [this message]
2022-09-28 22:28   ` Florian Fainelli
2022-09-29  6:40     ` Thomas Petazzoni
2022-09-30 22:05       ` Florian Fainelli
2022-10-01 19:07     ` Yann E. MORIN
2022-10-03 17:21       ` Florian Fainelli
2022-10-03 19:15         ` Yann E. MORIN
2023-04-17 19:58 ` Yann E. MORIN
2023-04-19  0:27   ` Florian Fainelli
2023-04-23 10:40 ` Peter Korsgaard

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=20220928233856.77bb191c@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@buildroot.org \
    --cc=f.fainelli@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 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.