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,
the arch/x86 maintainers <x86@kernel.org>
Subject: Re: [GIT PULL] kmemcheck fixlets (for -tip)
Date: Mon, 29 Sep 2008 09:54:36 +0200 [thread overview]
Message-ID: <20080929075436.GA11940@elte.hu> (raw)
In-Reply-To: <20080928180652.GA8500@localhost.localdomain>
* Vegard Nossum <vegard.nossum@gmail.com> wrote:
> Hi Ingo,
>
> Here is the fixlets branch, including bitfields API. I think it would
> be very nice if you could make this a *separate* branch in -tip, say
> kmemcheck-fixlets or so, as it may touch any part of the kernel and
> doesn't carry the acks of those maintainers.
>
> With these patches, you should be able to include kmemcheck in
> auto-testing again. At least it works for me :-)
>
> You may also kill tip/kmemcheck-dma, which has been integrated already.
branches are hard to kill in Git (anyone pushing back from a tree that
still has the old branch will re-create it). The name is sufficiently
generic so we keep keep it. The name can be reused in the future
eventually.
> The following changes since commit 9f24b3ed3058f022dad24f8304b9ad53adf5aa71:
> Vegard Nossum (1):
> x86: use REP MOVS instruction for memcpy if kmemcheck is enabled
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/vegard/kmemcheck.git fixlets-for-tip
>
> Vegard Nossum (6):
> 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: allocate struct siginfo with SLAB_NOTRACK
>
> drivers/ieee1394/csr1212.c | 2 ++
> drivers/ieee1394/nodemgr.c | 7 ++++++-
> include/linux/kmemcheck.h | 39 +++++++++++++++++++++++++++++++++++++++
> include/linux/skbuff.h | 31 +++++++++++++++++++------------
> include/net/inet_sock.h | 24 +++++++++++++++---------
> kernel/signal.c | 8 +++++++-
> net/core/skbuff.c | 8 ++++++++
> 7 files changed, 96 insertions(+), 23 deletions(-)
pulled into tip/kmemcheck-bitfields, thanks Vegard. I've also propagated
this new branch into the integration rules of auto-kmemcheck-next.
Ingo
next prev parent reply other threads:[~2008-09-29 7:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-28 18:06 [GIT PULL] kmemcheck fixlets (for -tip) Vegard Nossum
2008-09-29 7:54 ` Ingo Molnar [this message]
2008-09-29 7:59 ` Ingo Molnar
2008-09-29 8:55 ` Ingo Molnar
2008-09-29 9:13 ` Vegard Nossum
2008-09-29 9:25 ` Ingo Molnar
2008-09-29 9:43 ` Ingo Molnar
2008-09-29 11:13 ` Ingo Molnar
2008-09-29 11:57 ` kmemcheck: Caught 32-bit read from uninitialized memory (f6038ec0) Ingo Molnar
2008-09-29 13:14 ` Ingo Molnar
2008-10-05 12:42 ` Vegard Nossum
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=20080929075436.GA11940@elte.hu \
--to=mingo@elte.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
--cc=vegard.nossum@gmail.com \
--cc=x86@kernel.org \
/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