From: Maxin John <maxin.john@gmail.com>
To: Julien Olivain <ju.o@free.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2] package/mdadm: bump to version 4.6
Date: Sat, 25 Apr 2026 19:07:24 +0300 [thread overview]
Message-ID: <aezmvPtlpAFdf8Ub@Thor.home> (raw)
In-Reply-To: <0459c13f82431b7c833d30f3147b4578@free.fr>
Hi Julien,
On Sat, Apr 25, 2026 at 02:07:47PM +0200, Julien Olivain wrote:
> Hi Maxin,
>
> Thanks for the v2. This new 4.6 version is introducing 2 issues.
>
> On 25/04/2026 08:27, Maxin John wrote:
> > Drop upstreamed/backported patches.
> >
> > Release announcements:
> > 4.6:
> > https://lore.kernel.org/linux-raid/CALTww2_2pjjOSsVj-WT++m35555CjnPWokU7fut+HwUJVV-=ZQ@mail.gmail.com/
>
> First, it breaks the mdadm runtime test. See:
> https://gitlab.com/jolivain/buildroot/-/jobs/14088239652
>
> You can reproduce the issue with the command:
>
> utils/docker-run \
> support/testing/run-tests \
> -k -d dl -o output_folder tests.package.test_mdadm
>
> This new version asks a question and blocks the test.
>
> This commit should make sure the test keep working.
> So this can be fixed by passing the answer to the question.
> Adding "--bitmap=none" to the "mdadm --create" options should
> fix the issue. See:
> https://gitlab.com/buildroot.org/buildroot/-/blob/2026.02.1/support/testing/tests/package/test_mdadm.py?ref_type=tags#L72
>
> Also, this new version breaks with toolchains with old kernel headers. See:
> https://gitlab.com/jolivain/buildroot/-/jobs/14088277312
>
> You can reproduce the issue with the command:
>
> utils/test-pkg -p mdadm
>
> This is due to mdadm upstream commit
> 71574efb077131701b3da874df0045f259ca3448
> (in mdadm 4.0) which introduced a usage of MD_DISK_FAILFAST but was also
> including the definition. Then upstream commit
> f5889f9a1b8753a1472dfef9d025da2bae395239 (in mdadm 4.5) removed the
> usage of those local definitions to use the kernel instead.
> So mdadm has now a new requirement on Kernel headers >= 4.10.
>
> The bootlin-aarch64-glibc-old has 4.9 kernel headers and is now failing.
>
> Search for "BR2_TOOLCHAIN_HEADERS_AT_LEAST_" for examples.
>
> Could you add this new requirement in Config.in and the explanation in
> the commit log please?
>
> >
> > 4.5:
> > https://lore.kernel.org/linux-raid/CALTww293wnLE2+eZsZ42oyNZhS_cc2agB4GNqTz8j3xiP0ALWA@mail.gmail.com/
> >
> > 4.4:
> > https://lore.kernel.org/linux-raid/20241213121438.7ed6a0fd@mtkaczyk-private-dev/
> >
> > Upstream mdadm project has moved its primary development to GitHub:
> > https://github.com/md-raid-utilities/mdadm
> > Updated download site accordingly.
> >
> > Signed-off-by: Maxin John <maxin.john@gmail.com>
>
> Could you send an updated patch addressing those issues,
> please?
Thanks again for the detailed review and pointers. That was really helpful. I
will send a v3.
> Best regards,
>
> Julien.
Best Regards,
Maxin
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-04-25 16:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-25 6:27 [Buildroot] [PATCH v2] package/mdadm: bump to version 4.6 Maxin John
2026-04-25 12:07 ` Julien Olivain via buildroot
2026-04-25 16:07 ` Maxin John [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=aezmvPtlpAFdf8Ub@Thor.home \
--to=maxin.john@gmail.com \
--cc=buildroot@buildroot.org \
--cc=ju.o@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox