linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Oleg Nesterov <oleg@redhat.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Christoph Hellwig <hch@infradead.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
	Anton Arapov <anton@redhat.com>,
	Ananth N Mavinakayanahalli <ananth@in.ibm.com>,
	Jim Keniston <jkenisto@linux.vnet.ibm.com>,
	Jiri Olsa <jolsa@redhat.com>, Josh Stone <jistone@redhat.com>
Subject: Re: [PATCH] uprobes/core: handle breakpoint and signal step exception.
Date: Tue, 13 Mar 2012 06:20:16 +0100	[thread overview]
Message-ID: <20120313052016.GA27824@elte.hu> (raw)
In-Reply-To: <20120309073348.GA15570@elte.hu>


* Ingo Molnar <mingo@elte.hu> wrote:

> 
> * Srikar Dronamraju <srikar@linux.vnet.ibm.com> wrote:
> 
> > * Ingo Molnar <mingo@elte.hu> [2012-03-08 14:48:09]:
> > 
> > > 
> > > * Srikar Dronamraju <srikar@linux.vnet.ibm.com> wrote:
> > > 
> > > > @@ -233,9 +233,11 @@ static inline void __user *arch_compat_alloc_user_space(long len)
> > > >  
> > > >  	if (test_thread_flag(TIF_IA32)) {
> > > >  		sp = task_pt_regs(current)->sp;
> > > > +#ifdef CONFIG_X86_64
> > > >  	} else {
> > > >  		/* -128 for the x32 ABI redzone */
> > > >  		sp = __this_cpu_read(old_rsp) - 128;
> > > > +#endif
> > > >  	}
> > > >  
> > > >  	return (void __user *)round_down(sp - len, 16);
> > > 
> > > So 'sp' is undefined if that TIF check fails?
> > > 
> > > Also, on a 32-bit kernel the TIF check probably fails all the 
> > > time, because we don't set TIF_IA32 (and don't know that flag).
> > 
> > > 
> > > It would probably be better to make the whole helper inline 
> > > #ifdef 64-bit, it does not look very useful on 32-bit.
> > > 
> > 
> > arch_compat_alloc_user_space gets called from compat_alloc_user_space
> > which is arch agnostic and exported too.
> > 
> > So I will change this to
> > 
> > void __user *arch_compat_alloc_user_space(long len)
> > {
> >   	if (is_ia32_compat_task(current))
> >   		sp = task_pt_regs(current)->sp;
> > #ifdef CONFIG_X86_64
> >   	else
> >   		/* -128 for the x32 ABI redzone */
> >   		sp = __this_cpu_read(old_rsp) - 128;
> > #endif
> >   
> >   	return (void __user *)round_down(sp - len, 16);
> > }
> > 
> > where is_ia32_compat_task() is the new macro that you 
> > suggested we put in compat.h which would return true if the 
> > task is 32 bit emulated on x86_64 or running on i386 machine.
> > 
> > Hence we can avoid the case where sp is not set.
> 
> Ok - looks good at first glance.

It does not look good on a second glance though, once I checked 
your latest patches.

arch_compat_alloc_user_space() is arch agnostic on 
*CONFIG_COMPAT=y* kernels.

It's generally not available on 32-bit builds - CONFIG_COMPAT is 
a facility to provide 32-bit syscall compatibility on 64-bit 
kernels. Such a facility is not needed on 32-bit kernels.

So providing this:

> void __user *arch_compat_alloc_user_space(long len)
> {
>	if (is_ia32_compat_task(current))
>               sp = task_pt_regs(current)->sp;

on 32-bit systems makes little sense.

So ... instead of adding is_compat_task() to compat.h it would 
be better to add it to another x86 header (processor.h might be 
good but I have not checked very hard) and maybe name it 
is_32bit_task() or so, to make sure there's no confusion with 
CONFIG_COMPAT=y methods.

I.e. you could drop this patch altogether:

  x86/trivial: Fix 'old_rsp' undefined build failure when including asm/compat.h

And rework the is_ia32_compat_task() patch to use another header 
and to use the is_32bit_task() name. Also, you should double 
check whether the x32 execution model needs special 
consideration as well:

 #define TIF_IA32		17	/* IA32 compatibility process */
 #define TIF_X32		30	/* 32-bit native x86-64 binary */

otherwise uprobe will not work with x32 tasks properly.

Thanks,

	Ingo

  reply	other threads:[~2012-03-13  5:20 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-23 11:02 [PATCH] uprobes/core: handle breakpoint and signal step exception Srikar Dronamraju
2012-02-23 12:18 ` Anton Arapov
2012-02-24  5:31   ` Srikar Dronamraju
2012-02-27  9:12 ` Ingo Molnar
2012-02-28 13:26   ` Srikar Dronamraju
2012-02-28 13:52     ` Ingo Molnar
2012-02-28 14:17       ` Srikar Dronamraju
2012-02-28 14:27         ` Ingo Molnar
2012-03-08 13:18   ` Srikar Dronamraju
2012-03-08 13:48     ` Ingo Molnar
2012-03-09  6:28       ` Srikar Dronamraju
2012-03-09  7:33         ` Ingo Molnar
2012-03-13  5:20           ` Ingo Molnar [this message]
2012-03-13  5:42             ` Ingo Molnar
2012-03-13  5:47               ` Ingo Molnar
2012-03-13  9:24                 ` Srikar Dronamraju
2012-03-13  9:38                   ` Ingo Molnar
2012-02-27  9:24 ` Ingo Molnar

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=20120313052016.GA27824@elte.hu \
    --to=mingo@elte.hu \
    --cc=ananth@in.ibm.com \
    --cc=anton@redhat.com \
    --cc=hch@infradead.org \
    --cc=hpa@zytor.com \
    --cc=jistone@redhat.com \
    --cc=jkenisto@linux.vnet.ibm.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masami.hiramatsu.pt@hitachi.com \
    --cc=oleg@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=srikar@linux.vnet.ibm.com \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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).