From: Christoph Hellwig <hch@infradead.org>
To: Luca Di Maio <luca.dimaio1@gmail.com>
Cc: linux-xfs@vger.kernel.org, dimitri.ledkov@chainguard.dev,
smoser@chainguard.dev, djwong@kernel.org
Subject: Re: [PATCH v1] xfs: test reproducible builds
Date: Thu, 11 Dec 2025 21:28:01 -0800 [thread overview]
Message-ID: <aTun4Qs_X1NpNoij@infradead.org> (raw)
In-Reply-To: <20251211172531.334474-1-luca.dimaio1@gmail.com>
On Thu, Dec 11, 2025 at 06:25:31PM +0100, Luca Di Maio wrote:
> With the addition of the `-p` populate option, SOURCE_DATE_EPOCH and
> DETERMINISTIC_SEED support, it is possible to create fully reproducible
> pre-populated filesystems. We should test them here.
Cool, thanks a lot!
> +#
> +# parent pointer inject test
> +#
I don't think that is correct :)
> +. ./common/preamble
> +_begin_fstest auto quick parent
Same for the parent here. Instead of parent mkfs is a good group here.
> +
> +# get standard environment, filters and checks
This is kinda redundand.
> +IMG_SIZE="512M"
> +IMG_FILE="$TEST_DIR/xfs_reproducible_test.img"
> +PROTO_DIR="$(dirname "$0")"
So this is basically packing up tests/generic/ in xfstests
directory. Is that the best choice? It won't really have non-regular
files, so the exercise might be a bit limited vs creating a directory
in $TEST_DIR and adding all file types there.
> + # - DETERMINISTIC_SEED: uses fixed seed (0x53454544) instead of getrandom()
overly long line.
> +# Compute hash of the image file
> +_hash_image()
> +{
> + md5sum "$1" | awk '{print $1}'
md5sum is pretty outdated. But we're using it in all kinds of other
places in xfstests, so I think for now this is the right thing to use
here. Eventually we should switch everything over to a more modern
checksum.
next prev parent reply other threads:[~2025-12-12 5:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-11 17:25 [PATCH v1] xfs: test reproducible builds Luca Di Maio
2025-12-12 5:28 ` Christoph Hellwig [this message]
2025-12-12 8:09 ` Luca Di Maio
2025-12-12 8:11 ` Christoph Hellwig
2025-12-12 16:56 ` Luca Di Maio
2025-12-15 5:35 ` Christoph Hellwig
2025-12-15 14:45 ` Luca Di Maio
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=aTun4Qs_X1NpNoij@infradead.org \
--to=hch@infradead.org \
--cc=dimitri.ledkov@chainguard.dev \
--cc=djwong@kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=luca.dimaio1@gmail.com \
--cc=smoser@chainguard.dev \
/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