linux-kernel - Re: Linux 2.6.28-rc1

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: <20081024.153139.36591021.davem@davemloft.net>
Date:	Fri, 24 Oct 2008 15:31:39 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	torvalds@...ux-foundation.org
Cc:	alistair@...zero.co.uk, rjw@...k.pl, linux-kernel@...r.kernel.org
Subject: Re: Linux 2.6.28-rc1

From: Linus Torvalds <torvalds@...ux-foundation.org>
Date: Fri, 24 Oct 2008 08:17:53 -0700 (PDT)

> Now, _another_ part (and arguably the really core reason) of this problem 
> is that our Makefile rules for the asm include directory is weak and 
> unreliable in the presense of already-existing unexpected entries.

I guess we could use seperate "stamp" files to deal with this.

Along with the generated file "foo" there is a "foo.stamp" file
that is generated with "touch" after "foo" is built.

Then "foo"'s update rule is whether the "foo.stamp" is out of date
wrt. it's dependencies.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/