From: Oleg Nesterov <oleg@redhat.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Anton Arapov <anton@redhat.com>,
Kyle McMartin <kmcmarti@redhat.com>,
Srikar Dronamraju <srikar@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org
Subject: [GIT PULL] uprobes: misc bugfixes
Date: Mon, 8 Oct 2012 16:04:07 +0200 [thread overview]
Message-ID: <20121008140407.GA8034@redhat.com> (raw)
Ingo, please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/oleg/misc uprobes/core
Mostly bugfixes. Nothing really serious, but probably makes sense
for 3.7 anyway, everything looks straightforward enough.
Oleg Nesterov (19):
uprobes: Do not leak UTASK_BP_HIT if find_active_uprobe() fails
uprobes: Do not setup ->active_uprobe/state prematurely
uprobes: Fix UPROBE_SKIP_SSTEP checks in handle_swbp()
uprobes: Kill UTASK_BP_HIT state
uprobes: Move clear_thread_flag(TIF_UPROBE) to uprobe_notify_resume()
uprobes: Change write_opcode() to use FOLL_FORCE
uprobes: Change valid_vma() to demand VM_MAYEXEC rather than VM_EXEC
uprobes: Restrict valid_vma(false) to skip VM_SHARED vmas
uprobes: Kill set_swbp()->is_swbp_at_addr()
uprobes: Introduce copy_opcode(), kill read_opcode()
uprobes: Kill set_orig_insn()->is_swbp_at_addr()
uprobes: Simplify is_swbp_at_addr(), remove stale comments
uprobes/x86: Only rep+nop can be emulated correctly
uprobes: Don't return success if alloc_uprobe() fails
uprobes: Do not delete uprobe if uprobe_unregister() fails
uprobes: Fix handle_swbp() vs unregister() + register() race
uprobes: Introduce prepare_uprobe()
uprobes: Fix prepare_uprobe() race with itself
uprobes: Fix the racy uprobe->flags manipulation
arch/x86/kernel/signal.c | 4 +-
arch/x86/kernel/uprobes.c | 16 +--
include/linux/uprobes.h | 11 --
kernel/events/uprobes.c | 345 +++++++++++++++++++++------------------------
4 files changed, 165 insertions(+), 211 deletions(-)
reply other threads:[~2012-10-08 14:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20121008140407.GA8034@redhat.com \
--to=oleg@redhat.com \
--cc=anton@redhat.com \
--cc=kmcmarti@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox