From: Harvey Harrison <harvey.harrison@gmail.com>
To: ananth@in.ibm.com
Cc: Masami Hiramatsu <mhiramat@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] kprobes: Introduce is_kprobe_fault()
Date: Thu, 03 Jan 2008 09:36:46 -0800 [thread overview]
Message-ID: <1199381806.6323.109.camel@brick> (raw)
In-Reply-To: <20080103070526.GA7690@in.ibm.com>
On Thu, 2008-01-03 at 12:35 +0530, Ananth N Mavinakayanahalli wrote:
> On Wed, Jan 02, 2008 at 08:05:14PM -0800, Harvey Harrison wrote:
>
> Thanks for the cleanup...
>
> ...
>
> > diff --git a/arch/x86/mm/fault_32.c b/arch/x86/mm/fault_32.c
> > index a2273d4..f2e909b 100644
> > --- a/arch/x86/mm/fault_32.c
> > +++ b/arch/x86/mm/fault_32.c
> > @@ -33,28 +33,6 @@
> >
> > extern void die(const char *,struct pt_regs *,long);
> >
> > -#ifdef CONFIG_KPROBES
> > -static inline int notify_page_fault(struct pt_regs *regs)
> > -{
> > - int ret = 0;
> > -
> > - /* kprobe_running() needs smp_processor_id() */
> > - if (!user_mode_vm(regs)) {
> ^^^^^^^^^^^
> For x86_32, this check is important. See commit
> 6444541671bd821b950dbaafee70d65188198aa6 (Never allow int3 traps
> from V8086 mode to enter the kprobes handler) for precise reason why its
> user_mode_vm() and not user_mode() for x86_32.
>
> You'll need to make room for this check in the generic macro below...
Or just keep X86_32 using its existing notify_page_fault, everyone else
can use the new is_kprobe_fault. I'll wait for a bit and see if
the s390 or avr32 people respond before resending.
Harvey
prev parent reply other threads:[~2008-01-03 17:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-03 4:05 [PATCH] kprobes: Introduce is_kprobe_fault() Harvey Harrison
2008-01-03 4:49 ` Masami Hiramatsu
2008-01-03 7:05 ` Ananth N Mavinakayanahalli
2008-01-03 17:36 ` Harvey Harrison [this message]
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=1199381806.6323.109.camel@brick \
--to=harvey.harrison@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=ananth@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@redhat.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