From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <ankur.tyagi85@gmail.com>, <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core][PATCH 4/4] mdadm: upgrade 4.4 -> 4.5
Date: Fri, 30 Jan 2026 08:03:38 +0100 [thread overview]
Message-ID: <DG1QD2UPJMSH.2VRUB1QKCB6VG@bootlin.com> (raw)
In-Reply-To: <20260126102747.1077552-4-ankur.tyagi85@gmail.com>
On Mon Jan 26, 2026 at 11:27 AM CET, Ankur Tyagi via lists.openembedded.org wrote:
> From: Ankur Tyagi <ankur.tyagi85@gmail.com>
>
> Changelog:
> https://git.kernel.org/pub/scm/utils/mdadm/mdadm.git/tree/CHANGELOG.md?h=mdadm-4.5
>
> Replaced 0001-restripe.c-Use-_FILE_OFFSET_BITS-to-enable-largefile.patch
> with 0001-raid6check.c-restripe.c-Use-64-bit-off_t-across-both.patch as
> partial changes from first patch are part of the upstream version[1].
>
> Dropped xmalloc.patch which is part of upstream version[2].
>
> Also refreshed other patches.
>
> [1] https://github.com/md-raid-utilities/mdadm/commit/787cc1b60130b8031be59e49d54463c58cd8cf74
> [2] https://git.kernel.org/pub/scm/utils/mdadm/mdadm.git/commit/raid6check.c?h=mdadm-4.5&id=e0df6c4c984d564e9e40913727e916a6cd8f466e
>
> Signed-off-by: Ankur Tyagi <ankur.tyagi85@gmail.com>
> ---
Hi Ankur,
Thanks for your patch.
> --- a/meta/recipes-extended/mdadm/mdadm_4.4.bb
> +++ b/meta/recipes-extended/mdadm/mdadm_4.5.bb
> @@ -13,12 +13,11 @@ SRC_URI = "git://git.kernel.org/pub/scm/utils/mdadm/mdadm.git;protocol=https;bra
> file://0001-Fix-the-path-of-corosync-and-dlm-header-files-check.patch \
> file://mdadm.init \
> file://0001-Makefile-install-mdcheck.patch \
> - file://0001-restripe.c-Use-_FILE_OFFSET_BITS-to-enable-largefile.patch \
> file://0002-Create.c-include-linux-falloc.h-for-FALLOC_FL_ZERO_R.patch \
> - file://xmalloc.patch \
> + file://0001-raid6check.c-restripe.c-Use-64-bit-off_t-across-both.patch \
> "
You should also remove the two unused patches from git.
Also, we have a second issue: I suspect this upgrade is responsible of
some intermittent reproducibility issue. I already had it twice on my
branch:
AssertionError: The following deb packages are different and not in exclusion list:
/srv/pokybuild/yocto-worker/reproducible/build/build-st/reproducibleB-extended/tmp/deploy/deb/./x86-64-v3/mdadm_4.5-r0_amd64.deb
The following ipk packages are different and not in exclusion list:
/srv/pokybuild/yocto-worker/reproducible/build/build-st/reproducibleB-extended/tmp/deploy/ipk/./x86-64-v3/mdadm_4.5-r0_x86-64-v3.ipk
The following rpm packages are different and not in exclusion list:
/srv/pokybuild/yocto-worker/reproducible/build/build-st/reproducibleB-extended/tmp/deploy/rpm/./x86_64_v3/mdadm-4.5-r0.x86_64_v3.rpm
https://autobuilder.yoctoproject.org/valkyrie/#/builders/37/builds/3278
https://autobuilder.yoctoproject.org/valkyrie/#/builders/37/builds/3274
Corresponding diffoscope output can be found here:
https://valkyrie.yocto.io/pub/repro-fail/oe-reproducible-20260129-v__phvnk/packages/diff-html/
https://valkyrie.yocto.io/pub/repro-fail/oe-reproducible-20260129-5hbi93fk/packages/diff-html/
It looks like the difference is some path that is sometimes appearing as
"BINDIR/mdadm" and sometimes as "/sbin/mdadm".
I know these reproducibility issues are not the easiest ones to debug,
but I would appreciate if you could have a look for obvious failure
reasons.
Thanks,
Mathieu
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2026-01-30 7:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-26 10:27 [OE-core][PATCH 1/4] rgb: update 1.1.0 -> 1.1.1 ankur.tyagi85
2026-01-26 10:27 ` [OE-core][PATCH 2/4] glew: update 2.2.0 -> 2.3.1 ankur.tyagi85
2026-01-26 10:27 ` [OE-core][PATCH 3/4] stress-ng: update 0.19.06 -> 0.20.00 ankur.tyagi85
2026-01-26 10:27 ` [OE-core][PATCH 4/4] mdadm: upgrade 4.4 -> 4.5 ankur.tyagi85
2026-01-30 7:03 ` Mathieu Dubois-Briand [this message]
2026-01-30 7:44 ` Ankur Tyagi
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=DG1QD2UPJMSH.2VRUB1QKCB6VG@bootlin.com \
--to=mathieu.dubois-briand@bootlin.com \
--cc=ankur.tyagi85@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
/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.