linux-kernel - Re: [PATCH] kmemcheck: support for x86

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: <19f34abd0805180431r15ed93bbk68f5313bdeaa255a@mail.gmail.com>
Date:	Sun, 18 May 2008 13:31:41 +0200
From:	"Vegard Nossum" <vegard.nossum@...il.com>
To:	"Andi Kleen" <andi@...stfloor.org>
Cc:	"Pekka Enberg" <penberg@...helsinki.fi>,
	"Ingo Molnar" <mingo@...e.hu>, linux-kernel@...r.kernel.org,
	"Arjan van de Ven" <arjan@...ux.intel.com>
Subject: Re: [PATCH] kmemcheck: support for x86_64

On Sun, May 18, 2008 at 12:17 PM, Andi Kleen <andi@...stfloor.org> wrote:
>
>> Most of them look something like this:
>>
>> kmemcheck: Caught 8-bit read from freed memory (ffff81000780a904)
>> ifffffffifffffffifffffffifffffffifffffffifffffffifffffffifffffff
>>     ^
>>
>> and my theory so far is that X86_64 uses some currently unhandled
>> instruction set extensions like MMX, SSE, etc. (Not 3DNow! because we
>> have a dependency for that), for a fairly common operation
>
> No it shouldn't. Only SSE users are in the (broken) MD RAID code
>
> Most likely you don't decode REX correctly in some cases.

Thanks. You are right, but you are wrong.

All those #ifdef X86_64 should of course be CONFIG_X86_64... So none
of the 64-bit code was being compiled in. Good spotting, Vegard! :-(


Vegard

-- 
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
	-- E. W. Dijkstra, EWD1036
--
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/