From: Florian Bezdeka <florian.bezdeka@siemens.com>
To: Venkata.Pyla@toshiba-tsip.com, felix.moessbauer@siemens.com,
isar-users@googlegroups.com, Uladzimir Bely <ubely@ilbers.de>,
Anton Mikanovich <amikan@ilbers.de>
Cc: jan.kiszka@siemens.com, kazuhiro3.hayashi@toshiba.co.jp,
dinesh.kumar@toshiba-tsip.com, venkatapyla4@gmail.com,
Adithya.Balakumar@toshiba-tsip.com
Subject: Re: [PATCH 3/5] wic: use E2FSPROGS_FAKE_TIME and hash_seed to generate reproducible ext4 images
Date: Thu, 28 Dec 2023 09:47:33 +0100 [thread overview]
Message-ID: <efa0d43bcb95466033189f2278aab1d1f1c51472.camel@siemens.com> (raw)
In-Reply-To: <OS3PR01MB6856193633B9F60E01824814A49EA@OS3PR01MB6856.jpnprd01.prod.outlook.com>
On Thu, 2023-12-28 at 06:02 +0000, Venkata.Pyla@toshiba-tsip.com wrote:
> > -----Original Message-----
> > From: isar-users@googlegroups.com <isar-users@googlegroups.com> On Behalf
> > Of Venkata.Pyla@toshiba-tsip.com
> > Sent: Tuesday, December 12, 2023 7:37 PM
> > To: florian.bezdeka@siemens.com; felix.moessbauer@siemens.com; isar-
> > users@googlegroups.com
> > Cc: jan.kiszka@siemens.com; hayashi kazuhiro(林 和宏 DME
> > ○DIG□MPS○MP4) <kazuhiro3.hayashi@toshiba.co.jp>; dinesh
> > kumar(TSIP TMIEC ODG Porting) <dinesh.kumar@toshiba-tsip.com>
> > Subject: RE: [PATCH 3/5] wic: use E2FSPROGS_FAKE_TIME and hash_seed to
> > generate reproducible ext4 images
> >
> >
> >
> > > -----Original Message-----
> > > From: 'Florian Bezdeka' via isar-users <isar-users@googlegroups.com>
> > > Sent: Saturday, December 9, 2023 4:38 PM
> > > To: pyla venkata(TSIP TMIEC ODG Porting) <Venkata.Pyla@toshiba-
> > > tsip.com>; felix.moessbauer@siemens.com; isar-users@googlegroups.com
> > > Cc: jan.kiszka@siemens.com; hayashi kazuhiro(林 和宏 DME
> > > ○DIG□MPS○MP4) <kazuhiro3.hayashi@toshiba.co.jp>; dinesh
> > > kumar(TSIP TMIEC ODG Porting) <dinesh.kumar@toshiba-tsip.com>
> > > Subject: Re: [PATCH 3/5] wic: use E2FSPROGS_FAKE_TIME and hash_seed to
> > > generate reproducible ext4 images
> > >
> > > On Fri, 2023-12-08 at 18:14 +0000, Venkata.Pyla@toshiba-tsip.com wrote:
> > > > > -----Original Message-----
> > > > > From: 'MOESSBAUER, Felix' via isar-users
> > > > > <isar-users@googlegroups.com>
> > > > > Sent: Friday, December 8, 2023 4:04 PM
> > > > > To: isar-users@googlegroups.com; pyla venkata(TSIP TMIEC ODG
> > > > > Porting) <Venkata.Pyla@toshiba-tsip.com>
> > > > > Cc: Kiszka, Jan <jan.kiszka@siemens.com>; hayashi kazuhiro(林 和宏
> > > DME
> > > > > ○DIG□MPS○MP4) <kazuhiro3.hayashi@toshiba.co.jp>; dinesh
> > > > > kumar(TSIP TMIEC ODG Porting) <dinesh.kumar@toshiba-tsip.com>
> > > > > Subject: Re: [PATCH 3/5] wic: use E2FSPROGS_FAKE_TIME and
> > > > > hash_seed to generate reproducible ext4 images
> > > > >
> > > > > On Thu, 2023-12-07 at 21:11 +0530, venkata.pyla@toshiba-tsip.com
> > > wrote:
> > > > > > From: venkata pyla <venkata.pyla@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
> > > > >
> > > > > Hi!
> > > > >
> > > > > Did you also send this patch to OE?
> > > > > We need to integrate it there as well, as this is the basis for
> > > > > the ISAR
> > > plugins.
> > > >
> > > > Not shared yet, I will send to OE as well.
> > >
> > > We should follow "upstream first" here. Once OE has accepted the patch
> > > we will inherit it during next OE -> Isar update cycle.
> >
> > I have shared this patch to OE [1], hope I will get feedback from the community
> > and will support to fix this issue in the OE itself.
> >
> > [1] https://lists.openembedded.org/g/openembedded-core/message/192192
>
> This patch [1] has been merged now in upstream OE-core,
> now the required patches should be taken to ISAR, is there any timeline to bring the OE-core changes to ISAR or should we apply the required changes to ISAR manually?
>
> [1] https://github.com/openembedded/openembedded-core/commit/bb822ab75de0020572058090439b93cc56bbf7e0
That's great! Thanks for taking care.
I added two guys from Ilbers, maybe they have an update pending already
or can comment on the timeline. Anton, Uladzimir any comments?
In general it's a good idea to come up with a patch to speed things up.
The last update was done in 64af29bcc4b0 ("wic: Update to the latest
revision"). Might be used as inspiration.
Florian
>
> > >
> > > Maintainers: Do not apply it to Isar directly.
> > >
> > > >
> > > > >
> > > > > Best regards,
> > > > > Felix
> > > > >
> > > > > >
> > >
> > > --
> > > 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/f2563bb179d011f22de10d212600f6ef4c0cb284.camel%40siemens.com
> > > .
> >
> > --
> > 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/OS3PR01MB68566626DF8F78E4F73D2A45A48EA%40OS3PR01MB6856.jpn
> > prd01.prod.outlook.com.
next prev parent reply other threads:[~2023-12-28 8:47 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 [this message]
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
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=efa0d43bcb95466033189f2278aab1d1f1c51472.camel@siemens.com \
--to=florian.bezdeka@siemens.com \
--cc=Adithya.Balakumar@toshiba-tsip.com \
--cc=Venkata.Pyla@toshiba-tsip.com \
--cc=amikan@ilbers.de \
--cc=dinesh.kumar@toshiba-tsip.com \
--cc=felix.moessbauer@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
--cc=kazuhiro3.hayashi@toshiba.co.jp \
--cc=ubely@ilbers.de \
--cc=venkatapyla4@gmail.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