From: Michael Ellerman <michael@ellerman.id.au>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-arch@vger.kernel.org, linux-ia64@vger.kernel.org,
linux-kernel@vger.kernel.org, anil.s.keshavamurthy@intel.com,
linuxppc-dev@ozlabs.org, Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH 3/3] Make jprobes a little safer for users
Date: Tue, 26 Jun 2007 12:06:46 +1000 [thread overview]
Message-ID: <1182823606.6673.1.camel@concordia.ozlabs.ibm.com> (raw)
In-Reply-To: <20070625190057.c8dcb110.akpm@linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 1596 bytes --]
On Mon, 2007-06-25 at 19:00 -0700, Andrew Morton wrote:
> On Tue, 26 Jun 2007 11:48:51 +1000 (EST) Michael Ellerman <michael@ellerman.id.au> wrote:
>
> > I realise jprobes are a razor-blades-included type of interface, but
> > that doesn't mean we can't try and make them safer to use. This guy I
> > know once wrote code like this:
> >
> > struct jprobe jp = { .kp.symbol_name = "foo", .entry = "jprobe_foo" };
> >
> > And then his kernel exploded. Oops.
> >
> > This patch adds an arch hook, arch_deref_entry_point() (I don't like it either)
> > which takes the void * in a struct jprobe, and gives back the text address
> > that it represents.
> >
> > We can then use that in register_jprobe() to check that the entry point
> > we're passed is actually in the kernel text, rather than just some random
> > value.
> >
> > Signed-off-by: Michael Ellerman <michael@ellerman.id.au>
> > ---
> > arch/ia64/kernel/kprobes.c | 7 ++++++-
> > arch/powerpc/kernel/kprobes.c | 11 ++++++++---
> > kernel/kprobes.c | 9 +++++++++
>
> We're missing a declaration of arch_deref_entry_point() in some header file?
Yeah I guess. It's declared weak in kernel/kprobes.c, but there should
be a definition somewhere to make sure the three versions don't get out
of sync. I'll send a patch.
cheers
--
Michael Ellerman
OzLabs, IBM Australia Development Lab
wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)
We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-06-26 2:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-26 1:48 [PATCH 1/3] Make struct jprobe.entry a void * Michael Ellerman
2007-06-26 1:48 ` [PATCH 3/3] Make jprobes a little safer for users Michael Ellerman
2007-06-26 2:00 ` Andrew Morton
2007-06-26 2:06 ` Michael Ellerman [this message]
2007-06-26 5:53 ` Christoph Hellwig
2007-06-26 6:03 ` Michael Ellerman
2007-06-26 6:51 ` Andrew Morton
2007-06-26 6:19 ` Abhishek Sagar
2007-06-26 6:34 ` Michael Ellerman
2007-06-26 7:54 ` Abhishek Sagar
2007-06-26 1:48 ` [PATCH 2/3] Remove JPROBE_ENTRY() Michael Ellerman
2007-06-26 5:52 ` Christoph Hellwig
2007-06-26 3:51 ` [PATCH 1/3] Make struct jprobe.entry a void * Ananth N Mavinakayanahalli
2007-06-26 3:59 ` Ananth N Mavinakayanahalli
2007-06-26 4:35 ` Michael Ellerman
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=1182823606.6673.1.camel@concordia.ozlabs.ibm.com \
--to=michael@ellerman.id.au \
--cc=akpm@linux-foundation.org \
--cc=anil.s.keshavamurthy@intel.com \
--cc=hch@lst.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
/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;
as well as URLs for NNTP newsgroup(s).