From: Oleg Nesterov <oleg@redhat.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Anton Arapov <aarapov@redhat.com>,
David Smith <dsmith@redhat.com>,
"Frank Ch. Eigler" <fche@redhat.com>,
Srikar Dronamraju <srikar@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/1] uprobes: Fix the wrong usage of current->utask in uprobe_copy_process()
Date: Fri, 8 Nov 2013 16:57:14 +0100 [thread overview]
Message-ID: <20131108155714.GA26611@redhat.com> (raw)
Ingo,
I am stupid. aa59c53fd459 "uprobes: Change uprobe_copy_process()
to dup xol_area" needs the trivial fix, see 1/1. Sorry.
Perhaps I should add this patch to my tree and ask you to pull
this one-liner? Probably I can also add another "uprobes: Fix
the memory out of bound overwrite in copy_insn()" fix I sent
yesterday...
Oleg.
next reply other threads:[~2013-11-08 15:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-08 15:57 Oleg Nesterov [this message]
2013-11-08 15:57 ` [PATCH 1/1] uprobes: Fix the wrong usage of current->utask in uprobe_copy_process() Oleg Nesterov
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=20131108155714.GA26611@redhat.com \
--to=oleg@redhat.com \
--cc=aarapov@redhat.com \
--cc=dsmith@redhat.com \
--cc=fche@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