From: Oleg Nesterov <oleg@redhat.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Ananth N Mavinakayanahalli <ananth@in.ibm.com>,
Anton Arapov <anton@redhat.com>, Jovi Zhang <bookjovi@gmail.com>,
Rabin Vincent <rabin@rab.in>,
Srikar Dronamraju <srikar@linux.vnet.ibm.com>,
Steven Rostedt <rostedt@goodmis.org>,
linux-kernel@vger.kernel.org
Subject: [GIT PULL] uprobes: single-step cleanups + reg/unreg fix
Date: Mon, 19 Nov 2012 18:26:00 +0100 [thread overview]
Message-ID: <20121119172600.GA11012@redhat.com> (raw)
Ingo, please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/oleg/misc uprobes/core
- arch_uprobe_*_step() should die before arm port.
- "Use percpu_rw_semaphore to fix register/unregister vs dup_mmap() race"
fixes the serious bug, the "random" task can be killed after unregister.
Jovi Zhang (1):
uprobes: Fix misleading log entry
Oleg Nesterov (5):
uprobes/powerpc: Don't clear TIF_UPROBE in do_notify_resume()
uprobes/powerpc: Do not use arch_uprobe_*_step() helpers
uprobes/x86: Cleanup the single-stepping code
uprobes: Kill arch_uprobe_enable/disable_step() hooks
uprobes: Use percpu_rw_semaphore to fix register/unregister vs dup_mmap() race
Rabin Vincent (1):
uprobes: Flush cache after xol write
arch/powerpc/kernel/signal.c | 4 +--
arch/powerpc/kernel/uprobes.c | 6 ++++
arch/x86/kernel/uprobes.c | 54 ++++++++++++++--------------------------
include/linux/uprobes.h | 10 ++++++-
kernel/events/uprobes.c | 43 +++++++++++++++++++++-----------
kernel/fork.c | 2 +
kernel/trace/trace_uprobe.c | 2 +-
7 files changed, 65 insertions(+), 56 deletions(-)
next reply other threads:[~2012-11-19 17:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-19 17:26 Oleg Nesterov [this message]
2012-12-08 14:53 ` [GIT PULL] uprobes: single-step cleanups + reg/unreg fix 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=20121119172600.GA11012@redhat.com \
--to=oleg@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=ananth@in.ibm.com \
--cc=anton@redhat.com \
--cc=bookjovi@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rabin@rab.in \
--cc=rostedt@goodmis.org \
--cc=srikar@linux.vnet.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.