lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Thu, 03 Jan 2008 09:36:46 -0800
From:	Harvey Harrison <harvey.harrison@...il.com>
To:	ananth@...ibm.com
Cc:	Masami Hiramatsu <mhiramat@...hat.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] kprobes: Introduce is_kprobe_fault()

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



--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ