linux-kernel - Re: [PATCH V2] [X86] Fix potential issue on memmove

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: <4C6403A4.1040909@intel.com>
Date:	Thu, 12 Aug 2010 07:22:28 -0700
From:	"H. Peter Anvin" <h.peter.anvin@...el.com>
To:	"Ma, Ling" <ling.ma@...el.com>
CC:	Namhyung Kim <namhyung@...il.com>,
	"tglx@...utronix.de" <tglx@...utronix.de>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"mingo@...e.hu" <mingo@...e.hu>
Subject: Re: [PATCH V2] [X86] Fix potential issue on memmove

On 08/12/2010 07:15 AM, H. Peter Anvin wrote:
> On 08/11/2010 11:52 PM, Ma, Ling wrote:
>> Thanks, I will fix it in next version.
> 
> Also, please split this into two patches -- one for fixing memmove, and
> the other for re-enabling the alias avoidance in memcpy.
> 	
> 	-hpa
> 

Nevermind, the patch doesn't actually contain the x86/mem patch.

It's rather confusing to put "re-active patch id
a1e5278e40f16a4611264f8da9e557c16cb6f6ed" for a patch that was caught in
testing rather than ever included; it doesn't even exist under that
patch ID anymore.

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