linux-kernel - Re: [RFC] [patch 1/2] add non_init_kernel_text

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: <20071214075106.GA13249@in.ibm.com>
Date:	Fri, 14 Dec 2007 13:21:06 +0530
From:	Ananth N Mavinakayanahalli <ananth@...ibm.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Srinivasa Ds <srinivasa@...ibm.com>, linux-kernel@...r.kernel.org,
	Masami Hiramatsu <mhiramat@...hat.com>,
	Jim Keniston <jkenisto@...ibm.com>, rusty@...tcorp.com.au
Subject: Re: [RFC] [patch 1/2] add non_init_kernel_text_address

On Thu, Dec 13, 2007 at 11:09:16PM -0800, Andrew Morton wrote:
> On Fri, 14 Dec 2007 12:25:30 +0530 Srinivasa Ds <srinivasa@...ibm.com> wrote:
> 
> > Since __init functions are discarded and its memory freed once
> > initialization completes, It would be better if we enable kprobes 
> > to refuse probing __init functions. The attached patchset will do 
> > that.
> > 
> > This patch creates non_init_kernel_text_address() to identify
> > non_init text area.
> > 
> > Iam open to suggestions for a better functionname. 
> > 
> 
> It's not a great name.  One wonders how it handles __exit text, for example.

When registering kprobes on modules, we 'get' a module refcount so the
probed module doesn't disappear from under us. When the probe is
unregistered, we 'put' the refcount. That works great for __exit text.

> regular_kernel_text_address()?  Dunno.

Sounds better :-)

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/