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: <20081024192241.GA17080@uranus.ravnborg.org>
Date:	Fri, 24 Oct 2008 21:22:41 +0200
From:	Sam Ravnborg <sam@...nborg.org>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Alistair John Strachan <alistair@...zero.co.uk>,
	"Rafael J. Wysocki" <rjw@...k.pl>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Linux 2.6.28-rc1

On Fri, Oct 24, 2008 at 08:17:53AM -0700, Linus Torvalds wrote:
> 
> You can use "git clean -dfx" to force git to remove ignored files too. And 
> "make distclean" should have done it too.

I just checked and make mrproper / make distclean deletes the symlink
as expected.

> 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.
> 
> And it has caused problems before. For example, if you somehow made the 
> symlink not be a symlink at all (by using "cp -LR" for example), or a 
> symlink pointing to another architecture (changing architecture builds in 
> the same tree without doing a "make clean" in between), you historically 
> got really odd results.

We do not cover the "asm symlink became a dir" problem.
But when all archs has moved headers it is anyway implicitly covered.

	Sam
--
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/