From: Luca Barbieri <ldb@ldb.ods.org>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Christoph Hellwig <hch@infradead.org>,
Linus Torvalds <torvalds@transmeta.com>,
Linux-Kernel ML <linux-kernel@vger.kernel.org>,
"Vamsi Krishna S ." <vamsi@in.ibm.com>
Subject: Re: [PATCH] (re-xmit): kprobes for i386
Date: 21 Aug 2002 03:29:37 +0200 [thread overview]
Message-ID: <1029893377.24300.162.camel@ldb> (raw)
In-Reply-To: <20020820200453.407422C066@lists.samba.org>
[-- Attachment #1: Type: text/plain, Size: 735 bytes --]
> > > + if (kprobe_running() && kprobe_fault_handler(regs, trapnr))
> > > + return;
> > > if (!(regs->xcs & 3))
> > > goto kernel_trap;
> > The kprobe check should be after the kernel_trap label.
>
> No. The entire *point* of being able to register a kprobe fault
> handler is to be able to handle any kernel faults yourself if you want
> to.
It seems you have misunderstood my point.
My idea is that since kprobes are only used for kernel mode address, we
should move the kprobe check in the code that executes after we check
that the fault is happening in kernel mode.
Soemthing like this:
if (!(regs->xcs & 3))
goto kernel_trap;
[...]
kernel_trap:
if (kprobe_running() && kprobe_fault_handler(regs, trapnr))
return;
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2002-08-21 1:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-20 4:39 [PATCH] (re-xmit): kprobes for i386 Rusty Russell
2002-08-20 8:19 ` Christoph Hellwig
2002-08-20 10:25 ` Rusty Russell
2002-08-20 11:54 ` Luca Barbieri
[not found] ` <3D62365E.8030905@iram.es>
2002-08-20 14:06 ` Luca Barbieri
2002-08-20 19:29 ` Linus Torvalds
2002-08-21 1:03 ` Rusty Russell
2002-08-21 1:29 ` Luca Barbieri [this message]
2002-08-21 4:21 ` Rusty Russell
2002-08-21 8:31 ` Vamsi Krishna S .
2002-08-21 10:48 ` Rusty Russell
2002-08-21 12:33 ` Vamsi Krishna S .
-- strict thread matches above, loose matches on Subject: below --
2002-09-20 6:16 [PATCH] Re-xmit: " Rusty Russell
2002-08-12 8:18 [PATCH] (Re-xmit) " Rusty Russell
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=1029893377.24300.162.camel@ldb \
--to=ldb@ldb.ods.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=torvalds@transmeta.com \
--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