Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Romain Naour <romain.naour@smile.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/3] support/testing: bump prebuilt kernel to 5.10.202
Date: Fri, 05 Jan 2024 11:41:15 +0100	[thread overview]
Message-ID: <87r0iw3vw4.fsf@48ers.dk> (raw)
In-Reply-To: <20231206224422.16063-1-romain.naour@smile.fr> (Romain Naour's message of "Wed, 6 Dec 2023 23:44:20 +0100")

>>>>> "Romain" == Romain Naour <romain.naour@smile.fr> writes:

 > As reported on the mailing list [1], TestPolkitSystemd and
 > TestPolkitInitd are failing since we bumped the Bootlin toolchain
 > 2023.08 [2].

 > The issue is caused by expat (XML library) package detecting
 > arc4random_buf() introduced by glibc 2.36 [3].

 > With arc4random_buf() support enabled, expat hang Polkit while reading
 > its policy files (XML files) due to a lack of entropy on the system.

 > Upgrading the kernel allows to avoid such issue thanks to
 > random_get_entropy_fallback() introduced in 5.10.119 (backpored) [4].

 > Build the vexpress-v2p-ca9 (armv7) 5.10.202 using the kernel
 > configuration file found in /proc/config.gz but with additional kernel
 > options provided by SYSTEMD_LINUX_CONFIG_FIXUPS. Indeed some kernel
 > options requested by systemd were missing in 5.10.7 kernel.

 > Build the versatile-pb (armv5) kernel using the same kernel
 > configuration as qemu_arm_versatile_defconfig but with additional
 > kernel options like for vexpress-v2p-ca9. While at it, enable
 > IKCONFIG_PROC option to provide the kernel configuration at runtime
 > in /proc/config.gz.

 > Runtime tested:
 > https://gitlab.com/kubu93/buildroot/-/pipelines/1097887826 (tests.package.test_polkit.TestPolkit*)
 > https://gitlab.com/kubu93/buildroot/-/pipelines/1097705399 (tests.init.*)

 > Fixes:
 > https://gitlab.com/buildroot.org/buildroot/-/jobs/5689309948 (TestPolkitSystemd)
 > https://gitlab.com/buildroot.org/buildroot/-/jobs/5689309947 (TestPolkitInitd)

 > [1] http://lists.busybox.net/pipermail/buildroot/2023-December/680445.html
 > [2] 452365a385ef35e808eb2eb669d1e3227c7399dd
 > [3] https://sourceware.org/git/?p=glibc.git;a=commit;h=6f4e0fcfa2d2b0915816a3a3a1d48b4763a7dee2
 > [4] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=fdca775081527364621857957655207d83035376

 > Signed-off-by: Romain Naour <romain.naour@smile.fr>

Committed to 2023.11.x, thanks.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2024-01-05 10:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-06 22:44 [Buildroot] [PATCH 1/3] support/testing: bump prebuilt kernel to 5.10.202 Romain Naour
2023-12-06 22:44 ` [Buildroot] [PATCH 2/3] support/testing: InitSystemSystemdBaseOverlayfs: bump " Romain Naour
2024-01-05 10:41   ` Peter Korsgaard
2023-12-06 22:44 ` [Buildroot] [PATCH 3/3] support/testing: TestDtbocfg: " Romain Naour
2024-01-05 10:41   ` Peter Korsgaard
2023-12-09 20:57 ` [Buildroot] [PATCH 1/3] support/testing: bump prebuilt " Yann E. MORIN
2024-01-05 10:41 ` Peter Korsgaard [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=87r0iw3vw4.fsf@48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@buildroot.org \
    --cc=romain.naour@smile.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox