linux-kernel - Re: [PATCH 00/23] tracehook

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] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 17 Jul 2008 00:39:59 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Roland McGrath <roland@...hat.com>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Ingo Molnar <mingo@...e.hu>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 00/23] tracehook

On Thu, 17 Jul 2008 00:25:41 -0700 (PDT) Roland McGrath <roland@...hat.com> wrote:

> This patch series introduces the "tracehook" interface layer of inlines
> in <linux/tracehook.h>.
>
> ...
>
>  25 files changed, 1084 insertions(+), 188 deletions(-)

It's a strange time to be sending this.

We're in the middle of a massive dump from linux-next into mainline and
soon we'll be doing a more modest dump of -mm into mainline and I'm
tiptoeing around getting all anxious when people try to sneak
wasnt-in-linux-next stuff into mainline thus wrecking all my junk.

I'm largely in ignore-new-stuff mode as I'm trying to stabilise
the existing stuff for 2.6.27-rc1 and hopefully the subsystem
maintainers are in the same mode.

So, hum.  It's not a good time for anyone to be merging new
probably-2.6.28 material like this!

So for now, please let's just review the code and if it does get decent
review and if there are no unresolveable objections, please ask Stephen
to include this tree in linux-next.

That being said, the impact on existing code is fairly modest and we
could perhaps slip it into 2.6.27-rc1.  I haven't looked at it yet.

Still.  Strange timing!
--
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/