From: Ingo Molnar <mingo@kernel.org>
To: Oleg Nesterov <oleg@redhat.com>
Cc: Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <peterz@infradead.org>,
Srikar Dronamraju <srikar@linux.vnet.ibm.com>,
Ananth N Mavinakayanahalli <ananth@in.ibm.com>,
Anton Arapov <anton@redhat.com>,
linux-kernel@vger.kernel.org,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Subject: Re: [GIT PULL] (Was: uprobes: teach uprobes to clear MMF_HAS_UPROBES)
Date: Thu, 30 Aug 2012 10:18:47 +0200 [thread overview]
Message-ID: <20120830081847.GB3741@gmail.com> (raw)
In-Reply-To: <20120829175424.GA2732@redhat.com>
* Oleg Nesterov <oleg@redhat.com> wrote:
> On 08/27, Oleg Nesterov wrote:
> >
> > Srikar, this is still waiting for your review ;)
>
> I was informed that Srikar is travelling and can't review this seris.
>
> So I think it doesn't make sense to delay the already acked patches,
> the more testing the better ;) Yes, uprobe_munmap() looks strange,
> we should either remove it or apply this series. But we can do this
> later, and uprobes have other problems.
>
> Ingo, please pull from
>
> git://git.kernel.org/pub/scm/linux/kernel/git/oleg/misc uprobes
>
> Note: the patch from Sebastian wasn't acked by Srikar, but I hope
> this cleanup is simple enough.
>
> Oleg Nesterov (7):
> uprobes: Kill uprobes_state->count
> uprobes: Kill dup_mmap()->uprobe_mmap(), simplify uprobe_mmap/munmap
> uprobes: Change uprobe_mmap() to ignore the errors but check fatal_signal_pending()
> uprobes: Do not use -EEXIST in install_breakpoint() paths
> uprobes: Introduce MMF_HAS_UPROBES
> uprobes: Fold uprobe_reset_state() into uprobe_dup_mmap()
> uprobes: Remove "verify" argument from set_orig_insn()
>
> Sebastian Andrzej Siewior (1):
> uprobes: Remove check for uprobe variable in handle_swbp()
>
> Srikar Dronamraju (1):
> uprobes: Remove redundant lock_page/unlock_page
>
> include/linux/sched.h | 2 +
> include/linux/uprobes.h | 13 ++--
> kernel/events/uprobes.c | 159 +++++++++++++----------------------------------
> kernel/fork.c | 6 +--
> 4 files changed, 54 insertions(+), 126 deletions(-)
Pulled into tip:perf/core for v3.7, thanks a lot Oleg!
Ingo
next prev parent reply other threads:[~2012-08-30 8:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-19 16:40 [PATCH 0/3] uprobes: teach uprobes to clear MMF_HAS_UPROBES Oleg Nesterov
2012-08-19 16:40 ` [PATCH 1/3] uprobes: uprobes_treelock should not disable irqs Oleg Nesterov
2012-09-14 16:18 ` Srikar Dronamraju
2012-08-19 16:40 ` [PATCH 2/3] uprobes: introduce MMF_RECALC_UPROBES Oleg Nesterov
2012-09-14 16:32 ` Srikar Dronamraju
2012-08-19 16:40 ` [PATCH 3/3] uprobes: teach find_active_uprobe() to clear MMF_HAS_UPROBES Oleg Nesterov
2012-09-14 16:43 ` Srikar Dronamraju
2012-09-15 14:41 ` Oleg Nesterov
2012-08-27 17:44 ` [PATCH 0/3] uprobes: teach uprobes " Oleg Nesterov
2012-08-29 17:54 ` [GIT PULL] (Was: uprobes: teach uprobes to clear MMF_HAS_UPROBES) Oleg Nesterov
2012-08-30 8:18 ` Ingo Molnar [this message]
2012-09-14 17:12 ` [PATCH 0/3] uprobes: teach uprobes to clear MMF_HAS_UPROBES Srikar Dronamraju
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=20120830081847.GB3741@gmail.com \
--to=mingo@kernel.org \
--cc=ananth@in.ibm.com \
--cc=anton@redhat.com \
--cc=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=oleg@redhat.com \
--cc=peterz@infradead.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;
as well as URLs for NNTP newsgroup(s).