public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frederic Weisbecker <fweisbec@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Vegard Nossum <vegard.nossum@gmail.com>,
	Pekka Enberg <penberg@cs.helsinki.fi>,
	linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] kmemcheck updates for -tip
Date: Sun, 22 Feb 2009 18:00:45 +0100	[thread overview]
Message-ID: <20090222170044.GC6003@nowhere> (raw)
In-Reply-To: <20090222164419.GA28442@elte.hu>

On Sun, Feb 22, 2009 at 05:44:19PM +0100, Ingo Molnar wrote:
> 
> * Vegard Nossum <vegard.nossum@gmail.com> wrote:
> 
> > Hi,
> > 
> > Here are the latest kmemcheck developments. Changes are basically:
> > 
> > 1. Bitfield annotations.
> > 2. Fix REP handling on P4s.
> > 3. Page allocator hooks.
> > 
> > At boot, I get two false positives, in copy_mount_options() and
> > __dequeue_signal(). I've also seen two spontaneous floods of warnings from
> > somewhere in aio code, but I couldn't pinpoint exactly why things went
> > wrong. I guess it will need a bit more research.
> > 
> > 
> > Vegard
> > 
> > 
> > The following changes since commit 2215d76c949375d38b33f32580908accfffbb461:
> >   Ingo Molnar (1):
> >         Merge branch 'x86/core' into kmemcheck
> > 
> > are available in the git repository at:
> > 
> >   git://git.kernel.org/pub/scm/linux/kernel/git/vegard/kmemcheck.git for-tip
> > 
> > Vegard Nossum (12):
> >       kmemcheck: bitfield API
> >       net: use kmemcheck bitfields API for skbuff
> >       net: annotate bitfields in struct inet_sock
> >       ieee1394: annotate bitfield
> >       ieee1394/csr1212: fix false positive kmemcheck report
> >       kmemcheck: annotate inet_timewait_sock bitfields
> >       kmemcheck: disable fast string operations on P4 CPUs
> >       kmemcheck: rip out REP instruction emulation
> >       kmemcheck: add hooks for page- and sg-dma-mappings
> >       kmemcheck: don't track allocated page tables
> >       kmemcheck: add hooks for the page allocator
> >       kmemcheck: depend on !SLUB_DEBUG_ON
> > 
> >  arch/x86/Kconfig.debug             |    2 +-
> >  arch/x86/include/asm/dma-mapping.h |    6 ++
> >  arch/x86/include/asm/thread_info.h |    4 +-
> >  arch/x86/kernel/cpu/intel.c        |   23 +++++++
> >  arch/x86/mm/kmemcheck/kmemcheck.c  |  121 +-----------------------------------
> >  arch/x86/mm/kmemcheck/opcode.c     |   13 +----
> >  arch/x86/mm/kmemcheck/opcode.h     |    3 +-
> >  arch/x86/mm/kmemcheck/shadow.c     |    8 +++
> >  arch/x86/mm/pgtable.c              |   12 ++--
> >  drivers/ieee1394/csr1212.c         |    2 +
> >  drivers/ieee1394/nodemgr.c         |    7 ++-
> >  include/linux/gfp.h                |    5 ++
> >  include/linux/kmemcheck.h          |   72 ++++++++++++++++++++--
> >  include/linux/skbuff.h             |   33 ++++++----
> >  include/net/inet_sock.h            |   26 +++++---
> >  include/net/inet_timewait_sock.h   |   11 ++-
> >  mm/kmemcheck.c                     |   45 ++++++++++----
> >  mm/page_alloc.c                    |    8 +++
> >  mm/slab.c                          |   15 +++--
> >  mm/slub.c                          |   23 +++++--
> >  net/core/skbuff.c                  |    8 +++
> >  net/ipv4/inet_timewait_sock.c      |    3 +
> >  22 files changed, 252 insertions(+), 198 deletions(-)
> 
> Pulled into tip:kmemcheck and started testing it, thanks Vegard!
> 
> 	Ingo


BTW, I just tested kmemcheck (without these fixes pulled) and encountered some
troubles with the function graph tracer which hangs during the self tests.
As well as a message from hrtimer which tells its interrupt is too slow.

Well, I'm pulling latest -tip and will see.


> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/



  reply	other threads:[~2009-02-22 17:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-22 13:57 [GIT PULL] kmemcheck updates for -tip Vegard Nossum
2009-02-22 16:44 ` Ingo Molnar
2009-02-22 17:00   ` Frederic Weisbecker [this message]
2009-02-22 17:05     ` Sitsofe Wheeler
2009-02-22 17:06     ` Vegard Nossum
  -- strict thread matches above, loose matches on Subject: below --
2009-02-26 14:01 Vegard Nossum
2009-02-26 15:23 ` Ingo Molnar
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=20090222170044.GC6003@nowhere \
    --to=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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