linux-kernel - Re: x86-64: memset()/memcpy() not fully standards compliant

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: <73464.1325882419@turing-police.cc.vt.edu>
Date:	Fri, 06 Jan 2012 15:40:19 -0500
From:	Valdis.Kletnieks@...edu
To:	Jan Beulich <JBeulich@...e.com>
Cc:	mingo@...e.hu, tglx@...utronix.de, hpa@...or.com,
	Andi Kleen <andi@...stfloor.org>, linux-kernel@...r.kernel.org
Subject: Re: x86-64: memset()/memcpy() not fully standards compliant

On Thu, 05 Jan 2012 14:04:30 GMT, Jan Beulich said:
> Forever these two functions have been limited to deal with at most 4G
> at a time. While I cannot point out an in-tree user that would require
> larger sizes, it is now the second time that within our Xen kernel we got
> bitten by that limitation.

Wow.  Second time?  What the heck is the Xen kernel *doing* that it's
trying to do over 4G in a single memset/memcpy?

Content of type "application/pgp-signature" skipped