linux-kernel - Re: [PATCH resend] asm/types.h: All architectures use int-ll64.h in kernelspace

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] [day] [month] [year] [list]

Date:	Mon, 13 Feb 2012 02:59:32 +0000
From:	Arnd Bergmann <arnd@...db.de>
To:	Al Viro <viro@...iv.linux.org.uk>
Cc:	Geert Uytterhoeven <geert@...ux-m68k.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Randy Dunlap <rdunlap@...otime.net>,
	linux-arch@...r.kernel.org, linux-doc@...r.kernel.org,
	Linux Kernel Development <linux-kernel@...r.kernel.org>,
	David Howells <dhowells@...hat.com>
Subject: Re: [PATCH resend] asm/types.h: All architectures use int-ll64.h in kernelspace

On Saturday 11 February 2012, Al Viro wrote:

> Umm...  That has happened and yes, asm-generic/types.h is currently
> equivalent to asm-generic/int-ll64.h.  What exactly are you planning
> to do?  Just rename the latter to the former and do search-and-replace
> over the tree?  We still have places that pull int-l64.h, albeit only
> !__KERNEL__ ones (i.e. everything under #ifdef __KERNEL__ in there
> seems to be killable)...
> 
> AFAICS, for quite a few of those guys we can simply add bitsperlong.h
> and add types.h to generic-y; is that the plan?

Yes, I think both would be good cleanups. Maybe David Howells can comment
as well since his user api split is going to change that a bit:
We end up needing only a separate version of uapi/asm/types.h for
alpha/ia64/mips64/powerpc64, while the in-kernel file is ok.

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