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:	Thu, 4 Feb 2010 17:00:57 +0100
From:	Christoph Hellwig <hch@....de>
To:	Arnd Bergmann <arnd@...db.de>
Cc:	"H. Peter Anvin" <hpa@...or.com>,
	David Miller <davem@...emloft.net>, hch@....de,
	akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
	linux-arch@...r.kernel.org, tony.luck@...el.com,
	ralf@...ux-mips.org, kyle@...artin.ca, benh@...nel.crashing.org,
	schwidefsky@...ibm.com, heiko.carstens@...ibm.com,
	tglx@...utronix.de, mingo@...hat.com, viro@...iv.linux.org.uk
Subject: Re: [PATCH 4/6] improve sys_personality for compat architectures

On Thu, Feb 04, 2010 at 08:38:10AM +0100, Arnd Bergmann wrote:
> I think it would be better to have a consistent behavior across
> architectures, so /something/ should be changed. On x86, the unused
> sys32_personality function can probable just be removed, if nothing
> else.
> 
> If we can get everyone to agree with the x86 way of handling this,
> we can also remove all the special cases for sys32_personality in the
> other architectures.

Yes, this should be common over architectures.  Anyway, I expect there
to be some discussion until we've reached that point, so for now I'll
rebase patches 5 and 6 to not require this patch, and will send one
to kill the unused x86 implementation.  Whatever is the final outcome
can be implemented on top.

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