From: "Rusty Lynch" <rusty@linux.co.intel.com>
To: "Randy.Dunlap" <rddunlap@osdl.org>,
"Rusty Lynch" <rusty@linux.co.intel.com>
Cc: <vamsi@in.ibm.com>, <rusty@rustcorp.com.au>,
"lkml" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] kprobes for 2.5.47
Date: Tue, 12 Nov 2002 20:15:20 -0800 [thread overview]
Message-ID: <001401c28acb$47ab2d70$77d40a0a@amr.corp.intel.com> (raw)
In-Reply-To: <Pine.LNX.4.33L2.0211121906540.29150-100000@dragon.pdx.osdl.net>
Actually I'm not verifying the address correctly because I need to verify
a kernel mapped address is valid, not a user space address.
Anyone know how to verify a kernel space address is valid?
-rustyl
----- Original Message -----
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: "Rusty Lynch" <rusty@linux.co.intel.com>
Cc: <vamsi@in.ibm.com>; <rusty@rustcorp.com.au>; "lkml"
<linux-kernel@vger.kernel.org>
Sent: Tuesday, November 12, 2002 7:08 PM
Subject: Re: [PATCH] kprobes for 2.5.47
> On Tue, 12 Nov 2002, Rusty Lynch wrote:
>
> | When register_kprobe() is called with a bad addr, we crash the kernel.
> | Should it be the reponsibility of the caller, or the kernel to make sure
the
> | addr is ok?
> |
> | The kernel could check by adding a
> |
> | +unsigned short tmp;
> | ....
> | +if(__get_user(tmp, (unsigned short *)p->addr)) {
> | + ret = -EINVAL;
> | + goto out;
> | +}
> |
> | to register_kprobe()
>
> This looks good to me. Kernel should check user addresses.
>
> | > +int register_kprobe(struct kprobe *p)
> | > +{
> | > + int ret = 0;
> | > +
> | > + spin_lock_irq(&kprobe_lock);
> | > + if (get_kprobe(p->addr)) {
> | > + ret = -EEXIST;
> | > + goto out;
> | > + }
> | > + list_add(&p->list, &kprobe_table[hash_ptr(p->addr,
KPROBE_HASH_BITS)]);
> | > +
> | > + p->opcode = *p->addr;
> | > + *p->addr = BREAKPOINT_INSTRUCTION;
> | > + flush_icache_range(p->addr, p->addr + sizeof(kprobe_opcode_t));
> | > + out:
> | > + spin_unlock_irq(&kprobe_lock);
> | > + return ret;
> | > +}
> |
> | BTW, I have a stupid little sample char driver that reads in
address/message
> | pairs and then adds a probe that printk's the message at the address.
This
> | was just my way of learning how to use kprobes. Should I post it? I
would
> | love to get feedback on what I did wrong, but I hate to spam the list.
>
> I'd like to see it, but from a learning POV instead of telling
> you what you did wrong with it.
>
> Thanks.
> --
> ~Randy
> "I read part of it all the way through." -- Samuel Goldwyn
next prev parent reply other threads:[~2002-11-13 4:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-12 11:20 Vamsi Krishna S .
2002-11-13 1:58 ` Rusty Lynch
2002-11-13 3:08 ` Randy.Dunlap
2002-11-13 4:15 ` Rusty Lynch [this message]
2002-11-13 7:22 ` Vamsi Krishna S .
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='001401c28acb$47ab2d70$77d40a0a@amr.corp.intel.com' \
--to=rusty@linux.co.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.org \
--cc=rusty@rustcorp.com.au \
--cc=vamsi@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
Powered by JetHome