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]
Date:	Sat, 25 Oct 2008 00:51:21 +0200
From:	Sam Ravnborg <sam@...nborg.org>
To:	David Miller <davem@...emloft.net>
Cc:	torvalds@...ux-foundation.org, alistair@...zero.co.uk, rjw@...k.pl,
	linux-kernel@...r.kernel.org
Subject: Re: Linux 2.6.28-rc1

On Fri, Oct 24, 2008 at 03:31:39PM -0700, David Miller wrote:
> 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.

I remember I made an attempt doing so long time ago for
the asm symlink. But why it failed for me I dunno.

We used this trick in many archs before
but as part of the header move to arch/$ARCH we have killed
almost all uses of symlink to reach certain files.

The asm symlink is only used by asm-offsett.h for most archs these
days and when I get around to it I will fix that too so we
can kill it entirely.

But first we need to move all archs headers to arch/$ARCH.
And we are getting there.

	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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ