linux-kernel - Re: [GIT PULL] kmemcheck for mainline

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <84144f020906160921s234b0095k654c75e2e6bfe6dd@mail.gmail.com>
Date:	Tue, 16 Jun 2009 19:21:57 +0300
From:	Pekka Enberg <penberg@...helsinki.fi>
To:	Vegard Nossum <vegard.nossum@...il.com>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Ingo Molnar <mingo@...e.hu>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] kmemcheck for mainline

On Mon, Jun 15, 2009 at 5:59 PM, Vegard Nossum<vegard.nossum@...il.com> wrote:
> I redid the tree by rebasing. I've backported and incorporated fixes except
> in the (few) cases where multiple authors were involved, in order to preserve
> authorship information. I rebased against the same version that the previous
> pull request was merged to; this allows us to easily view the difference
> between the two pull requests (minus the top commit, which is a merge with
> your latest tree):
>
>  $ git diff kmemcheck/for-linus..kmemcheck/for-linus2^
>
> and account for any discrepancies (see the bottom of this e-mail). I've
> tested the new tree on x86 and x86_64 with and without kmemcheck.

Looks good to me. Ingo, if Linus doesn't pull this for -rc1, I think
you should nuke the kmemcheck branch in -tip and use this instead,
right?

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