public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Vegard Nossum <vegard.nossum@gmail.com>
Cc: linux-kernel@vger.kernel.org,
	Pekka Enberg <penberg@cs.helsinki.fi>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] kmemcheck: lazy checking for MOVS instructions
Date: Sun, 14 Sep 2008 17:21:36 +0200	[thread overview]
Message-ID: <20080914152136.GF29290@elte.hu> (raw)
In-Reply-To: <19f34abd0809121009o81f2705ve083209a4af23b5d@mail.gmail.com>


* Vegard Nossum <vegard.nossum@gmail.com> wrote:

> On Fri, Sep 12, 2008 at 11:06 AM, Ingo Molnar <mingo@elte.hu> wrote:
> >> From: Vegard Nossum <vegard.nossum@gmail.com>
> >> Date: Thu, 11 Sep 2008 17:31:07 +0200
> >> Subject: [PATCH] kmemcheck: lazy checking for MOVS instructions
> >>
> >> This patch adds the support for lazy (as opposed to eager) checking
> >> for [REP] MOVS instructions (mostly used in memcpy()). This means that
> >> if both the source and destination addresses are tracked by kmemcheck,
> >> we copy the shadow memory instead of checking that it is initialized.
> >>
> >> In this way, we get rid of a few more false positives.
> >
> > looks good to me. I've applied it to tip/kmemcheck - but can zap it and
> > pull your for-tip branch as well.
> 
> Please zap, I believe it contains an error :-)
> 
> In short, when reading/writing the shadow memory of the second page in 
> a page-boundary-crossing memory access, the offsets into the second 
> shadow page will be wrong (off by up to 8 bytes). It's a pretty 
> obscure case, but it would be nice to have it fixed. Will send a pull 
> request later.

ok, zapped it.

	Ingo

      reply	other threads:[~2008-09-14 15:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-11 15:46 [PATCH] kmemcheck: lazy checking for MOVS instructions Vegard Nossum
2008-09-12  9:06 ` Ingo Molnar
2008-09-12 17:09   ` Vegard Nossum
2008-09-14 15:21     ` Ingo Molnar [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=20080914152136.GF29290@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=penberg@cs.helsinki.fi \
    --cc=vegard.nossum@gmail.com \
    /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