From: Andrew Morton <akpm@linux-foundation.org>
To: Srinivasa Ds <srinivasa@in.ibm.com>
Cc: linux-kernel@vger.kernel.org, ananth@in.ibm.com,
Masami Hiramatsu <mhiramat@redhat.com>,
Jim Keniston <jkenisto@us.ibm.com>,
rusty@rustcorp.com.au
Subject: Re: [RFC] [patch 1/2] add non_init_kernel_text_address
Date: Thu, 13 Dec 2007 23:09:16 -0800 [thread overview]
Message-ID: <20071213230916.cd30de8c.akpm@linux-foundation.org> (raw)
In-Reply-To: <200712141225.30099.srinivasa@in.ibm.com>
On Fri, 14 Dec 2007 12:25:30 +0530 Srinivasa Ds <srinivasa@in.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.
regular_kernel_text_address()? Dunno.
next prev parent reply other threads:[~2007-12-14 7:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-14 6:55 [RFC] [patch 1/2] add non_init_kernel_text_address Srinivasa Ds
2007-12-14 6:57 ` [RFC] [patch 2/2] Refuse kprobe insertion on __init section code Srinivasa Ds
2007-12-14 7:09 ` Andrew Morton [this message]
2007-12-14 7:51 ` [RFC] [patch 1/2] add non_init_kernel_text_address Ananth N Mavinakayanahalli
2007-12-18 4:57 ` Rusty Russell
2007-12-18 6:46 ` Srinivasa Ds
2007-12-18 7:23 ` Rusty Russell
2007-12-19 5:11 ` Rusty Russell
2008-01-01 6:34 ` Srinivasa Ds
2007-12-14 9:30 ` Srinivasa Ds
2007-12-14 10:17 ` Srinivasa Ds
2007-12-14 12:46 ` Johannes Weiner
2007-12-17 10:15 ` Srinivasa Ds
2007-12-17 10:20 ` [RFC] [patch 2/2] Refuse kprobe insertion on __init section code Srinivasa Ds
2007-12-14 9:34 ` Srinivasa Ds
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=20071213230916.cd30de8c.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ananth@in.ibm.com \
--cc=jkenisto@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@redhat.com \
--cc=rusty@rustcorp.com.au \
--cc=srinivasa@in.ibm.com \
/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