Merge request for kmemleak patches

Merge request for kmemleak patches

[Catalin Marinas]

Hi Stephen,

There are a few more kmemleak patches for the upcoming merging window
(the first one will be pushed before). Could you please pull them into
the -next tree? Thanks.


The following changes since commit 4be3bd7849165e7efa6b0b35a23d6a3598d97465:
  Linus Torvalds (1):
        Linux 2.6.31-rc4

are available in the git repository at:

  git://linux-arm.org/linux-2.6.git kmemleak

Catalin Marinas (8):
      kmemleak: Protect the seq start/next/stop sequence by rcu_read_lock()
      kmemleak: Dump object information on request
      kmemleak: Allow rescheduling during an object scanning
      kmemleak: Mark the early log buffer as __initdata
      kmemleak: Save the stack trace for early allocations
      kmemleak: Do not report alloc_bootmem blocks as leaks
      kmemleak: Inform kmemleak about kernel stack allocation
      kmemleak: Always scan the task stacks

Sergey Senozhatsky (1):
      kmemleak: Printing of the objects hex dump

 Documentation/kmemleak.txt         |   12 +-
 arch/x86/include/asm/thread_info.h |    7 +-
 arch/x86/kernel/process.c          |    1 +
 include/linux/kmemleak.h           |   18 ++--
 kernel/fork.c                      |    7 +-
 mm/bootmem.c                       |    6 +-
 mm/kmemleak.c                      |  199 ++++++++++++++++++++++++++----------
 7 files changed, 179 insertions(+), 71 deletions(-)

-- 
Catalin

Re: Merge request for kmemleak patches

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 991 bytes --]

Hi Catalin,

On Tue, 28 Jul 2009 10:15:59 +0100 Catalin Marinas <catalin.marinas@arm.com> wrote:
>
> There are a few more kmemleak patches for the upcoming merging window
> (the first one will be pushed before). Could you please pull them into
> the -next tree? Thanks.
> 
>   git://linux-arm.org/linux-2.6.git kmemleak

I have added the tree back for tomorrow.

What I tell everyone: all patches/commits in the tree/series must
have been:

	posted to a relevant mailing list
	reviewed
	unit tested
	destined for the next merge window (or the current release)

*before* they are included.  The linux-next tree is for integration
testing and to lower the impact of conflicts between subsystems in the
next merge window.

Basically, this should be just what you would send to Linus (or ask him
to fetch).  It is allowed to be rebased if you deem it necessary.
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]