public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Adithya Balakumar <adithya190298@gmail.com>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH 3/5] wic: use E2FSPROGS_FAKE_TIME and hash_seed to generate reproducible ext4 images
Date: Fri, 5 Jul 2024 05:13:33 -0700 (PDT)	[thread overview]
Message-ID: <3d9226f6-f046-445e-9edc-e107111c2437n@googlegroups.com> (raw)
In-Reply-To: <03db06fb48cc803750b0bdc79682cd140c027681.camel@siemens.com>


[-- Attachment #1.1: Type: text/plain, Size: 2911 bytes --]

Hi Felix,

I saw your mail regarding your attempt to make ext4 filesystem images from 
IMAGE_CMD:ext4 reproducible. 
If you don't mind, could you briefly explain what was the problem you faced 
in achieving this? 
I am also trying to understand on how to achieve the same.

Thanks and Regards,
Adithya Balakumar


On Tuesday, April 23, 2024 at 2:47:11 PM UTC+5:30 MOESSBAUER, Felix wrote:

On Thu, 2023-12-07 at 21:11 +0530, venkat...@toshiba-tsip.com wrote: 
> From: venkata pyla <venkat...@toshiba-tsip.com> 
> 
> E2FSPROGS_FAKE_TIME: sets fixed times for the inodes in the file 
> system. 
> hash_seed: creates reproducible directory indexes in the file system. 
> 
> Reference commit in e2fsprogs: 
> e1f7100643a46456be107b33098f6034b0835e6d 
> 
> Signed-off-by: venkata pyla <venkat...@toshiba-tsip.com> 
> --- 
>  scripts/lib/wic/partition.py | 11 +++++++++++ 
>  1 file changed, 11 insertions(+) 
> 
> diff --git a/scripts/lib/wic/partition.py 
> b/scripts/lib/wic/partition.py 
> index e50871b8..90b2c037 100644 
> --- a/scripts/lib/wic/partition.py 
> +++ b/scripts/lib/wic/partition.py 
> @@ -280,6 +280,17 @@ class Partition(): 
>   
>          extraopts = self.mkfs_extraopts or "-F -i 8192" 
>   
> +        if os.getenv('SOURCE_DATE_EPOCH'): 
> +            sde_time = int(os.getenv('SOURCE_DATE_EPOCH')) 
> +            pseudo = "export E2FSPROGS_FAKE_TIME=%s;%s" % (sde_time, 
> pseudo) 
> + 
> +            # Set hash_seed to generate deterministic directory 
> indexes 
> +            namespace = uuid.UUID("e7429877-e7b3-4a68-a5c9- 
> 2f2fdf33d460") 
> +            if self.fsuuid: 
> +                namespace = uuid.UUID(self.fsuuid) 
> +            hash_seed = str(uuid.uuid5(namespace, str(sde_time))) 
> +            extraopts += " -E hash_seed=%s" % hash_seed 
> + 

Hi, while reworking the SDE in ISAR, I stumbled upon this as well. 
This patch only covers the .wic part, but we need a similar patch for 
the IMAGE_CMD:ext4 as well. I tried to mimic the pattern there, but I 
was not able to make the .ext4 build reproducible (the diff indicated 
that the inodes are still shuffled around). This makes me wonder if 
mke2fs.ext4 even supports producing a reproducible rootfs. 

Have you been able to create a bit-by-bit identical .wic of an ext4 
partition? 

Best regards, 
Felix 

>          label_str = "" 
>          if self.label: 
>              label_str = "-L %s" % self.label 

-- 
Siemens AG, Technology 
Linux Expert Center 


-- 
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/isar-users/3d9226f6-f046-445e-9edc-e107111c2437n%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 4108 bytes --]

  reply	other threads:[~2024-07-05 12:46 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AQHaKSPYp2dXzOOhJUivzLFOKAgd4rF2a70A>
2023-12-07 15:41 ` [PATCH 0/5] Make ext4 images reproducible venkata.pyla
2023-12-07 15:41   ` [PATCH 1/5] linux-module: Use debug-prefix-map to build modules deterministically venkata.pyla
2023-12-08 10:27     ` MOESSBAUER, Felix
2023-12-07 15:41   ` [PATCH 2/5] wic: Set file system uuid to ext4 partitions venkata.pyla
2023-12-07 15:41   ` [PATCH 3/5] wic: use E2FSPROGS_FAKE_TIME and hash_seed to generate reproducible ext4 images venkata.pyla
2023-12-08 10:33     ` MOESSBAUER, Felix
2023-12-08 18:14       ` Venkata.Pyla
2023-12-09 11:07         ` Florian Bezdeka
2023-12-12 14:06           ` Venkata.Pyla
2023-12-28  6:02             ` Venkata.Pyla
2023-12-28  8:47               ` Florian Bezdeka
2023-12-28 10:10                 ` Anton Mikanovich
2024-03-13 10:01                   ` Adithya.Balakumar
2024-03-13 16:00                     ` Anton Mikanovich
2024-03-14  4:37                       ` Adithya.Balakumar
2024-04-25  6:24                       ` MOESSBAUER, Felix
2024-04-25  6:30                         ` Jan Kiszka
2024-04-25  7:02                           ` MOESSBAUER, Felix
2024-04-26  8:58                         ` Anton Mikanovich
2024-04-23  9:17     ` MOESSBAUER, Felix
2024-07-05 12:13       ` Adithya Balakumar [this message]
2024-07-08 10:43         ` 'MOESSBAUER, Felix' via isar-users
     [not found]           ` <CAM=oSXcw+sH3VYsstvDmRbLTK-H0ncFEbuqOhG2R0_P4bUYXjw@mail.gmail.com>
2024-07-08 11:12             ` Adithya.Balakumar
2023-12-07 15:41   ` [PATCH 4/5] wic: honor the SOURCE_DATE_EPOCH in case of updated fstab venkata.pyla
2023-12-07 15:41   ` [PATCH 5/5] wic: make ext2/3/4 images reproducible venkata.pyla
2023-12-08 10:29   ` [PATCH 0/5] Make ext4 " MOESSBAUER, Felix
2023-12-08 18:12     ` Venkata.Pyla

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=3d9226f6-f046-445e-9edc-e107111c2437n@googlegroups.com \
    --to=adithya190298@gmail.com \
    --cc=isar-users@googlegroups.com \
    /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