linux-kernel - Re: [PATCH 1/3] Make struct jprobe.entry a void *

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]

Message-ID: <20070626035946.GA20460@in.ibm.com>
Date:	Tue, 26 Jun 2007 09:29:46 +0530
From:	Ananth N Mavinakayanahalli <ananth@...ibm.com>
To:	Michael Ellerman <michael@...erman.id.au>
Cc:	<linux-kernel@...r.kernel.org>, <linuxppc-dev@...abs.org>,
	<linux-ia64@...r.kernel.org>, <linux-arch@...r.kernel.org>,
	Andrew Morton <akpm@...l.org>, Christoph Hellwig <hch@....de>,
	<anil.s.keshavamurthy@...el.com>
Subject: Re: [PATCH 1/3] Make struct jprobe.entry a void *

On Tue, Jun 26, 2007 at 11:48:50AM +1000, Michael Ellerman wrote:
> ---
> 
> It isn't obvious where kprobes patches should go, is anyone "the" maintainer?
> Instead I've just sent this to everyone who'd touched the code lately, or
> might be otherwise interested.

There isn't a single maintainer for the kprobes infrastructure as it
contains quite a bit of low level arch specific code. The working model
currently is that the patches are sent to lkml with a cc to the
maintainers listed, as you've rightly done.

Ananth
-
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/