mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Vegard Nossum" <vegard.nossum@gmail.com>
To: "Andi Kleen" <andi@firstfloor.org>
Cc: "Pekka Enberg" <penberg@cs.helsinki.fi>,
	"Ingo Molnar" <mingo@elte.hu>,
	linux-kernel@vger.kernel.org,
	"Arjan van de Ven" <arjan@linux.intel.com>
Subject: Re: [PATCH] kmemcheck: support for x86_64
Date: Sun, 18 May 2008 13:31:41 +0200	[thread overview]
Message-ID: <19f34abd0805180431r15ed93bbk68f5313bdeaa255a@mail.gmail.com> (raw)
In-Reply-To: <48300248.7050701@firstfloor.org>

On Sun, May 18, 2008 at 12:17 PM, Andi Kleen <andi@firstfloor.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

      reply	other threads:[~2008-05-18 11:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-17 23:04 Vegard Nossum
2008-05-18 10:17 ` Andi Kleen
2008-05-18 11:31   ` Vegard Nossum [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=19f34abd0805180431r15ed93bbk68f5313bdeaa255a@mail.gmail.com \
    --to=vegard.nossum@gmail.com \
    --cc=andi@firstfloor.org \
    --cc=arjan@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=penberg@cs.helsinki.fi \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®