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: <49A5E28F.5050209@zytor.com>
Date:	Wed, 25 Feb 2009 16:30:07 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Arnd Bergmann <arnd@...db.de>
CC:	Sam Ravnborg <sam@...nborg.org>,
	Kyle McMartin <kyle@...radead.org>,
	Ingo Molnar <mingo@...e.hu>,
	Jaswinder Singh Rajput <jaswinderrajput@...il.com>,
	mingo@...hat.com, dwmw2@...radead.org,
	linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org
Subject: Re: [patch 0/7] Use strict kernel types to fix the world

Arnd Bergmann wrote:
> On Thursday 26 February 2009, H. Peter Anvin wrote:
>>> I split out netfilter, DRM and MTD, because of both
>>> size and potentially controversial changes.
>> I take it this supercedes your previous monolithic patch?
> 
> Patch 1/7 supercedes my previous patch and is still as monolithic,
> except for the separate 6/7 hunk. I only split the integer type
> patches by subsystem, but I did these from scratch now.
> 
> Patch 7/7 is a new one, based on your input from the last time
> we discussed it.

6/7 we already had in -tip, apparently.

I'm really of two minds regarding the patches that replace pure data 
types (2/7-5/7).  Part of me thinks it would be better to do this via a 
script in make headers_install, but another part of me thinks that that 
is a recipe for missing includes.

However, if subsystem maintainers are sharing headers with other 
platforms, it's probably the only sane road to go.

	-hpa

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