From: Artem Bityutskiy <dedekind1@gmail•com>
To: Greg KH <gregkh@suse•de>
Cc: anil_ravindranath@pmc-sierra•com, mchehab@redhat•com,
mac@melware•de, aacraid@adaptec•com,
linux-mtd@lists•infradead.org, allan.stephens@windriver•com,
hpa@zytor•com, t.sailer@alumni•ethz.ch, gwingerde@gmail•com,
x86@kernel•org, elf@buici•com, cluster-devel@redhat•com,
ccaulfie@redhat•com, mingo@redhat•com, dougthompson@xmission•com,
dwmw2@infradead•org, linux-media@vger•kernel.org,
jon.maloy@ericsson•com, arnaud.giersch@free•fr,
linux-kbuild@vger•kernel.org, IvDoorn@gmail•com,
teigland@redhat•com, tony.olech@elandigitalsystems•com,
apw@canonical•com, linux-hams@vger•kernel.org,
tglx@linutronix•de, swhiteho@redhat•com,
linux-arm-kernel@lists•infradead.org, linux-edac@vger•kernel.org,
Michal Marek <mmarek@suse•cz>,
linux-scsi@vger•kernel.org, netdev@vger•kernel.org,
linux-usb@vger•kernel.org, linux-wireless@vger•kernel.org,
linux-kernel@vger•kernel.org, davem@davemloft•net,
James.Bottomley@suse•de, tipc-discussion@lists•sourceforge.net,
chuanxiao.dong@intel•com, paulus@samba•org,
linuxppc-dev@lists•ozlabs.org,
bluesmoke-devel@lists•sourceforge.net
Subject: Re: [PATCH 00/34] Make kernel build deterministic
Date: Tue, 05 Apr 2011 22:24:07 +0300 [thread overview]
Message-ID: <1302031447.2608.41.camel@koala> (raw)
In-Reply-To: <20110405154918.GA31337@suse.de>
On Tue, 2011-04-05 at 08:49 -0700, Greg KH wrote:
> On Tue, Apr 05, 2011 at 04:58:47PM +0200, Michal Marek wrote:
> >
> > Hi,
> >
> > this series makes it possible to build bit-identical kernel image and
> > modules from identical sources. Of course the build is already
> > deterministic in terms of behavior of the code, but the various
> > timestamps embedded in the object files make it hard to compare two
> > builds, for instance to verify that a makefile cleanup didn't
> > accidentally change something. A prime example is /proc/config.gz, which
> > has both a timestamp in the gzip header and a timestamp in the payload
> > data. With this series applied, a script like this will produce
> > identical kernels each time:
>
> Very nice stuff. Do you want to take the individual patches through one
> of your trees, or do you mind if the subsystem maintainers take them
> through theirs?
But unfortunately, it is very easy to break this and for sure it'll be
broken very soon.
So additionally, I'd suggest:
1. Instrument checkpatch.pl and make it err or warn on timestamps.
2. Probably instrument linux-next to rise a warning when people break
this.
--
Best Regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2011-04-05 19:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-05 14:58 [PATCH 00/34] Make kernel build deterministic Michal Marek
2011-04-05 14:58 ` [PATCH 03/34] powerpc: Call gzip with -n Michal Marek
2011-04-05 14:58 ` [PATCH 05/34] powerpc: Use the deterministic mode of ar Michal Marek
2011-04-05 15:49 ` [PATCH 00/34] Make kernel build deterministic Greg KH
2011-04-05 18:16 ` James Bottomley
2011-04-05 18:29 ` Mauro Carvalho Chehab
2011-04-05 18:44 ` Greg KH
2011-04-05 19:24 ` Artem Bityutskiy [this message]
2011-04-06 8:57 ` Ingo Molnar
2011-04-06 9:07 ` Michal Marek
2011-04-06 9:25 ` Artem Bityutskiy
2011-04-06 9:23 ` Michal Marek
2011-04-06 9:01 ` Ingo Molnar
2011-05-05 15:22 ` [PATCH v2] powerpc: Use the deterministic mode of ar Michal Marek
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=1302031447.2608.41.camel@koala \
--to=dedekind1@gmail$(echo .)com \
--cc=IvDoorn@gmail$(echo .)com \
--cc=James.Bottomley@suse$(echo .)de \
--cc=aacraid@adaptec$(echo .)com \
--cc=allan.stephens@windriver$(echo .)com \
--cc=anil_ravindranath@pmc-sierra$(echo .)com \
--cc=apw@canonical$(echo .)com \
--cc=arnaud.giersch@free$(echo .)fr \
--cc=bluesmoke-devel@lists$(echo .)sourceforge.net \
--cc=ccaulfie@redhat$(echo .)com \
--cc=chuanxiao.dong@intel$(echo .)com \
--cc=cluster-devel@redhat$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=dougthompson@xmission$(echo .)com \
--cc=dwmw2@infradead$(echo .)org \
--cc=elf@buici$(echo .)com \
--cc=gregkh@suse$(echo .)de \
--cc=gwingerde@gmail$(echo .)com \
--cc=hpa@zytor$(echo .)com \
--cc=jon.maloy@ericsson$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-edac@vger$(echo .)kernel.org \
--cc=linux-hams@vger$(echo .)kernel.org \
--cc=linux-kbuild@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-media@vger$(echo .)kernel.org \
--cc=linux-mtd@lists$(echo .)infradead.org \
--cc=linux-scsi@vger$(echo .)kernel.org \
--cc=linux-usb@vger$(echo .)kernel.org \
--cc=linux-wireless@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=mac@melware$(echo .)de \
--cc=mchehab@redhat$(echo .)com \
--cc=mingo@redhat$(echo .)com \
--cc=mmarek@suse$(echo .)cz \
--cc=netdev@vger$(echo .)kernel.org \
--cc=paulus@samba$(echo .)org \
--cc=swhiteho@redhat$(echo .)com \
--cc=t.sailer@alumni$(echo .)ethz.ch \
--cc=teigland@redhat$(echo .)com \
--cc=tglx@linutronix$(echo .)de \
--cc=tipc-discussion@lists$(echo .)sourceforge.net \
--cc=tony.olech@elandigitalsystems$(echo .)com \
--cc=x86@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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