linux-kernel - Re: Kbuild: how to cleanly retrieve information compilation about the last build

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <81798.1302983165@localhost>
Date:	Sat, 16 Apr 2011 15:46:05 -0400
From:	Valdis.Kletnieks@...edu
To:	Francis Moreau <francis.moro@...il.com>
Cc:	Sam Ravnborg <sam@...nborg.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Kbuild: how to cleanly retrieve information compilation about the last build

On Sat, 16 Apr 2011 17:57:23 +0200, Francis Moreau said:

> The user modify a file, then instead of calling 'make' (because he
> forgets) run the script that send the kernel image through the net on
> a test machine. Since the user had already compiled the kernel before,
>  the kernel image exists but is outdated.

As I said, this is an example of a broken development environment, or
possibly a broken developer. :)

> How can a script detect this case if it doesn't call 'make' in its turn ?

Why do you care about detecting it without calling make?  Just go ahead and
*do* it, if the kernel is up to date it won't take long.  With a completely
cold cache, it takes about 90 seconds on my laptop.  Cache-hot is closer to 45
seconds. If that's too long, buy the developer a real machine or a compile
farm.  If that's a problem, you'll need to put the developer inside a script
that enforces "you *vill* do dis, then you *vill* do dat" fascism so the
programmer never gets a chance to do something you didn't expect.

Content of type "application/pgp-signature" skipped