uprobes, x86: Fix _TIF_UPROBE vs _TIF_NOTIFY_RESUME
authorAndy Lutomirski <luto@amacapital.net>
Fri, 21 Nov 2014 21:26:07 +0000 (13:26 -0800)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Sat, 6 Dec 2014 23:57:16 +0000 (15:57 -0800)
commitcd624598ec9c269ffb57c698bc83c3ad4c3a245a
tree24bbf101393bc8b82144d03fd14b1a704340776a
parent7b58b42442f7e5e8194e23f22e9cedd9543f8354
uprobes, x86: Fix _TIF_UPROBE vs _TIF_NOTIFY_RESUME

commit 82975bc6a6df743b9a01810fb32cb65d0ec5d60b upstream.

x86 call do_notify_resume on paranoid returns if TIF_UPROBE is set but
not on non-paranoid returns.  I suspect that this is a mistake and that
the code only works because int3 is paranoid.

Setting _TIF_NOTIFY_RESUME in the uprobe code was probably a workaround
for the x86 bug.  With that bug fixed, we can remove _TIF_NOTIFY_RESUME
from the uprobes code.

Reported-by: Oleg Nesterov <oleg@redhat.com>
Acked-by: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
Acked-by: Borislav Petkov <bp@suse.de>
Signed-off-by: Andy Lutomirski <luto@amacapital.net>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
arch/x86/include/asm/thread_info.h
kernel/events/uprobes.c