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

Message-Id: <4F0AB384020000780006B1C2@nat28.tlf.novell.com>
Date:	Mon, 09 Jan 2012 08:29:40 +0000
From:	"Jan Beulich" <JBeulich@...e.com>
To:	<Valdis.Kletnieks@...edu>
Cc:	<mingo@...e.hu>, "Andi Kleen" <andi@...stfloor.org>,
	<tglx@...utronix.de>, <linux-kernel@...r.kernel.org>,
	<hpa@...or.com>
Subject: Re: x86-64: memset()/memcpy() not fully standards compliant

>>> On 06.01.12 at 21:40, <Valdis.Kletnieks@...edu> wrote:
> 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?

Please see my other reply to Andi for what data structures are
affected here (and starting at what total memory sizes).

Jan

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