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: Pekka Enberg <penberg@cs.helsinki.fi>, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] kmemcheck updates for -tip
Date: Thu, 26 Feb 2009 16:23:58 +0100	[thread overview]
Message-ID: <20090226152358.GA352@elte.hu> (raw)
In-Reply-To: <20090226140147.GA2824@damson.getinternet.no>


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

> Hi,
> 
> The following changes since commit 8f5bd505f147bcd57c627e8599cbcc6b082312d4:
>   Ingo Molnar (1):
>         Merge branch 'for-tip' of git://git.kernel.org/.../vegard/kmemcheck into kmemcheck
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/vegard/kmemcheck.git for-tip
> 
> Pekka Enberg (7):
>       kmemcheck: Disable SLUB and SLAB debugging when kmemcheck is enabled
>       kmemcheck: remove forward declarations from error.c
>       kmemcheck: make initialization message less confusing
>       kmemcheck: remove multiple ifdef'd definitions of the same global variable
>       kmemcheck: move 64-bit ifdef out of kmemcheck_opcode_decode()
>       kmemcheck: missing whitespace in do_page_fault()
>       kmemcheck: use kmemcheck_pte_lookup() instead of open-coding it
> 
> Vegard Nossum (9):
>       kmemcheck: fix an incorrect BUG_ON()
>       kmemcheck: fix shadow updates that cross page boundaries
>       crypto: don't track xor test pages with kmemcheck
>       x86: don't use MMX/SSE in xor routines if kmemcheck is compiled in
>       kmemcheck: reverse dependencies between DEBUG_PAGEALLOC and KMEMCHECK
>       kmemcheck: depend on DEBUG_KERNEL
>       c2port: annotate bitfield for kmemcheck
>       kmemcheck (bitfields): don't actually initialize the bitfield
>       net: annotate struct sock bitfield
> 
>  arch/x86/Kconfig.debug            |    6 +-
>  arch/x86/include/asm/xor.h        |    5 ++
>  arch/x86/mm/fault.c               |    2 +-
>  arch/x86/mm/kmemcheck/error.c     |  137 ++++++++++++++++++-------------------
>  arch/x86/mm/kmemcheck/kmemcheck.c |   20 ++---
>  arch/x86/mm/kmemcheck/opcode.c    |    9 ++-
>  arch/x86/mm/kmemcheck/shadow.c    |   38 +++++++++-
>  crypto/xor.c                      |    7 ++-
>  drivers/misc/c2port/core.c        |    2 +
>  include/linux/c2port.h            |    7 ++-
>  include/linux/kmemcheck.h         |    6 +-
>  include/net/sock.h                |    8 ++-
>  lib/Kconfig.debug                 |    4 +-
>  net/core/sock.c                   |    2 +
>  14 files changed, 151 insertions(+), 102 deletions(-)

pulled, thank Vegard!

	Ingo

  reply	other threads:[~2009-02-26 15:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-26 14:01 [GIT PULL] kmemcheck updates for -tip Vegard Nossum
2009-02-26 15:23 ` Ingo Molnar [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-02-22 13:57 Vegard Nossum
2009-02-22 16:44 ` Ingo Molnar
2009-02-22 17:00   ` Frederic Weisbecker
2009-02-22 17:05     ` Sitsofe Wheeler
2009-02-22 17:06     ` Vegard Nossum
2008-07-01 20:18 [git pull] " Vegard Nossum
2008-07-01 20:24 ` Ingo Molnar

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=20090226152358.GA352@elte.hu \
    --to=mingo@elte.hu \
    --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