All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Matthew Weber <matt@thewebers.ws>
Cc: Buildroot List <buildroot@buildroot.org>,
	 "Yann E. MORIN" <yann.morin.1998@free.fr>,
	"Arnout Vandecappelle (Essensium/Mind)" <arnout@mind.be>
Subject: Re: [Buildroot] [PATCH v3 3/3] support/scripts/check-host-bins: add new check on host binaries/libs
Date: Thu, 27 Aug 2026 07:33:25 +0200	[thread overview]
Message-ID: <ao_Loa791DyV_cMi@windsurf> (raw)
In-Reply-To: <CAFt09wMrVryrn14zaNKfjvAbk_Whpw=PQ2k=QWFScq2qNHtQ5w@mail.gmail.com>

Hello Matt,

On Wed, Aug 26, 2026 at 11:19:37PM -0500, Matthew Weber wrote:

> I did some testing and found the musl library needs added to the
> whitelist for Alpine.  I also added libraries to the scan which added
> more changes then what I could easily include here.  Here's my mocked
> up check-host-bins and test script.  The test case 5 was modeled after
> the distro tests that xen does to target different containers to find
> whitelist gaps.

Thanks for the testing. Instead of having a full new version of the
script with all fixes mixed together, do you think you could spit out
each fix as an independent patch, so that the changes can more easily
be reviewed? Especially some fixes don't seem necessarily related to
the new library check, but would be applicable to the existing
check-host-rpath code.

> https://gist.github.com/matthew-l-weber/34fae15a4319a81462961eadf0e31164
> 
> Some of this was AI generated, does Buildroot have any rules around AI use?

As far as I'm aware, we don't have rules around AI use. I'm also using
AI to help in some of my recent Buildroot work.

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:[~2026-08-27  5:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-25 21:41 [Buildroot] [PATCH v3 0/3] Improve checking of host binaries Thomas Petazzoni via buildroot
2026-08-25 21:41 ` [Buildroot] [PATCH v3 1/3] support/scripts/check-host-rpath: fix shellcheck issues Thomas Petazzoni via buildroot
2026-08-25 21:42 ` [Buildroot] [PATCH v3 2/3] support/scripts/check-host-rpath: rename to check-host-bins Thomas Petazzoni via buildroot
2026-08-25 21:42 ` [Buildroot] [PATCH v3 3/3] support/scripts/check-host-bins: add new check on host binaries/libs Thomas Petazzoni via buildroot
2026-08-27  4:19   ` Matthew Weber
2026-08-27  5:33     ` Thomas Petazzoni via buildroot [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=ao_Loa791DyV_cMi@windsurf \
    --to=buildroot@buildroot.org \
    --cc=arnout@mind.be \
    --cc=matt@thewebers.ws \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=yann.morin.1998@free.fr \
    /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.