From: Catalin Marinas <catalin.marinas@arm•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: linux-next <linux-next@vger•kernel.org>
Subject: Merge request for kmemleak patches
Date: Tue, 28 Jul 2009 10:15:59 +0100 [thread overview]
Message-ID: <1248772559.17665.12.camel@pc1117.cambridge.arm.com> (raw)
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
next reply other threads:[~2009-07-28 9:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-28 9:15 Catalin Marinas [this message]
2009-07-28 11:00 ` Merge request for kmemleak patches Stephen Rothwell
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=1248772559.17665.12.camel@pc1117.cambridge.arm.com \
--to=catalin.marinas@arm$(echo .)com \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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