qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Stefan Weil <sw@weilnetz.de>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Anthony Liguori <aliguori@us.ibm.com>,
	Markus Armbruster <armbru@redhat.com>,
	qemu-devel@nongnu.org, Luiz Capitulino <lcapitulino@redhat.com>,
	Blue Swirl <blauwirbel@gmail.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] makefile: detect corrupted elf files
Date: Sun, 26 May 2013 16:11:21 +0300	[thread overview]
Message-ID: <20130526131121.GB6865@redhat.com> (raw)
In-Reply-To: <51A2048B.1060305@weilnetz.de>

On Sun, May 26, 2013 at 02:48:11PM +0200, Stefan Weil wrote:
> Am 26.05.2013 14:31, schrieb Michael S. Tsirkin:
> > On Sun, May 26, 2013 at 10:12:21AM +0100, Peter Maydell wrote:
> >> On 26 May 2013 08:35, Michael S. Tsirkin <mst@redhat.com> wrote:
> >>> On Sat, May 25, 2013 at 05:32:24PM +0000, Blue Swirl wrote:
> >>>> Another way to handle this would be to enhance GCC and linker to use
> >>>> atomic operations when producing or combining object files. The tools
> >>>> could also print a SHA of the object which the next user should
> >>>> verify. Even better, the object files should include a robust checksum
> >>>> to ensure integrity.
> >>> I think we can make the makefile more robust. It can create a temporary
> >>> file in same directory and rename when ready. This will prevent
> >>> corrupted files from appearing in the first place.
> >> I definitely think individual project makefiles are the wrong place
> >> to fix this. If create-as-temp-and-rename is useful functionality
> >> it needs to go in the compiler so that everybody benefits.
> > This will not help users on existing systems.
> > Also it's not just compiler. We'd have to do it in linker,
> > asm, ... lots of work.
> > You are wellcome to implement this in compiler/linker/etc if you like
> > but we will still want to handle it in our makefile as well.
> >
> >> Or you
> >> could write yourself a cc wrapper that did the renaming and use
> >> configure's --cc= flag.
> >>
> >> thanks
> >> -- PMM
> > We also run lots of scripts in our makefiles. Would you like
> > to also change each of them individually? Add wrapper scripts for e.g.
> > python? What's the benefit as compared to just fixing it all in one
> > place in the makefile?
> 
> 
> GNU make automatically removes .o files which were built
> because of a Makefile rule if that rule returns an error, so
> OOM or compiler crashes should not result in corrupted .o
> files.

Not if make itself is killed.

> The same applies to other kinds of files built by
> make.

Another problem is power failures and other cases of sudden reboot.

> 
> If there are corrupted files, we have to look whether the
> Makefile rules for those files are correct (or exist at all).
> Are there other Open Source projects which try to detect
> corrupted elf files? I know none.
> 
> Regards
> Stefan W.
> 

It saves me time, at least.
I can keep it out of tree if it rubs others the wrong way
for some reason, it's no big deal.
If I have some spare time I might code up the more
generic thing with create then rename for all files,
if I do we can discuss that.

-- 
MST

  reply	other threads:[~2013-05-26 13:11 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-21 21:46 [Qemu-devel] [PATCH] makefile: detect corrupted elf files Michael S. Tsirkin
2013-05-21 22:01 ` Peter Maydell
2013-05-21 22:09   ` Michael S. Tsirkin
2013-05-22  7:44     ` Markus Armbruster
2013-05-22  8:37       ` Michael S. Tsirkin
2013-05-22  8:38         ` Peter Maydell
2013-05-22  8:43           ` Paolo Bonzini
2013-05-22  8:52             ` Michael S. Tsirkin
2013-05-22  9:22               ` Paolo Bonzini
2013-05-22  9:42                 ` Michael S. Tsirkin
2013-05-22 10:40                   ` Paolo Bonzini
2013-05-22 10:50                     ` Michael S. Tsirkin
2013-05-22 10:51                       ` Paolo Bonzini
2013-05-22 11:09                         ` Michael S. Tsirkin
2013-05-22 11:12                           ` Paolo Bonzini
2013-05-22 11:35                             ` Michael S. Tsirkin
2013-05-25 17:32                               ` Blue Swirl
2013-05-26  7:35                                 ` Michael S. Tsirkin
2013-05-26  9:12                                   ` Peter Maydell
2013-05-26 12:31                                     ` Michael S. Tsirkin
2013-05-26 12:48                                       ` Stefan Weil
2013-05-26 13:11                                         ` Michael S. Tsirkin [this message]
2013-05-26 13:36                                       ` Peter Maydell
2013-05-26 13:40                                         ` Michael S. Tsirkin
2013-05-26 18:20                                           ` Blue Swirl
2013-05-26 18:24                                             ` Michael S. Tsirkin
2013-05-26 19:28                                               ` Blue Swirl
2013-05-26 20:15                                                 ` Michael S. Tsirkin
2013-05-26 20:29                                                   ` Blue Swirl
2013-05-26 20:55                                                     ` Michael S. Tsirkin
2013-05-28 10:33                                                     ` Michael S. Tsirkin
2013-05-26 21:03                                               ` Anthony Liguori
2013-05-22  8:46           ` Michael S. Tsirkin
2013-05-22  9:48 ` Stefan Hajnoczi
2013-05-22 10:00   ` Michael S. Tsirkin

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=20130526131121.GB6865@redhat.com \
    --to=mst@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=armbru@redhat.com \
    --cc=blauwirbel@gmail.com \
    --cc=lcapitulino@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=sw@weilnetz.de \
    /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;
as well as URLs for NNTP newsgroup(s).