public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Oleg Nesterov <oleg@redhat.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Ananth N Mavinakayanahalli <ananth@in.ibm.com>,
	Anton Arapov <aarapov@redhat.com>,
	David Smith <dsmith@redhat.com>,
	"Frank Ch. Eigler" <fche@redhat.com>,
	Martin Cermak <mcermak@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Ralf Baechle <ralf@linux-mips.org>,
	Srikar Dronamraju <srikar@linux.vnet.ibm.com>,
	linux-kernel@vger.kernel.org
Subject: [GIT PULL] uprobes: fix fork() with the pending ret-probe(s)
Date: Sat, 19 Oct 2013 15:02:12 +0200	[thread overview]
Message-ID: <20131019130212.GA27109@redhat.com> (raw)

Ingo, please pull from

  git://git.kernel.org/pub/scm/linux/kernel/git/oleg/misc uprobes/core

This fixes the serious bug, a forked process crashes if it returns
from the probed function called by its parent, this cc's stable.

Also the minor fix from Ralf.

Oleg Nesterov (6):
      uprobes: Change the callsite of uprobe_copy_process()
      uprobes: Introduce __create_xol_area()
      uprobes: Teach __create_xol_area() to accept the predefined vaddr
      uprobes: Change uprobe_copy_process() to dup return_instances
      uprobes: Change uprobe_copy_process() to dup xol_area
      uprobes: Teach uprobe_copy_process() to handle CLONE_VFORK

Ralf Baechle (1):
      uprobes: Remove the wrong __weak attribute

 include/linux/uprobes.h |    6 +-
 kernel/events/uprobes.c |  156 ++++++++++++++++++++++++++++++++++++-----------
 kernel/fork.c           |    2 +-
 3 files changed, 124 insertions(+), 40 deletions(-)


             reply	other threads:[~2013-10-19 13:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-19 13:02 Oleg Nesterov [this message]
2013-10-19 13:18 ` [GIT PULL] uprobes: fix fork() with the pending ret-probe(s) 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=20131019130212.GA27109@redhat.com \
    --to=oleg@redhat.com \
    --cc=aarapov@redhat.com \
    --cc=ananth@in.ibm.com \
    --cc=dsmith@redhat.com \
    --cc=fche@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcermak@redhat.com \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=ralf@linux-mips.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox