From: Oleg Nesterov <oleg@redhat.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Anton Arapov <aarapov@redhat.com>,
Srikar Dronamraju <srikar@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org
Subject: [GIT PULL] uprobes: uprobe_copy_process() and copy_insn() fixes
Date: Sat, 9 Nov 2013 17:18:57 +0100 [thread overview]
Message-ID: <20131109161857.GA17484@redhat.com> (raw)
Ingo, please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/oleg/misc uprobes/core
I do not like to spam you, but I think that at least the 1st patch
should be merged now, along with other retprobe && fork fixed.
The 1st one-liner fixes the typo in the recently merged aa59c53fd459
"uprobes: Change uprobe_copy_process() to dup xol_area", a ret-probed
child still can crash.
The 2nd patch fixes the easy-to-trigger kernel crash. This bug is very
old, but fortunately only root can enable uprobes.
Oleg Nesterov (2):
uprobes: Fix the wrong usage of current->utask in uprobe_copy_process()
uprobes: Fix the memory out of bound overwrite in copy_insn()
kernel/events/uprobes.c | 49 +++++++++++++++++++++++------------------------
1 files changed, 24 insertions(+), 25 deletions(-)
next reply other threads:[~2013-11-09 16:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-09 16:18 Oleg Nesterov [this message]
2013-11-11 8:46 ` [GIT PULL] uprobes: uprobe_copy_process() and copy_insn() fixes 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=20131109161857.GA17484@redhat.com \
--to=oleg@redhat.com \
--cc=aarapov@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;
as well as URLs for NNTP newsgroup(s).