From: "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: Oleg Nesterov <oleg@redhat.com>,
Srikar Dronamraju <srikar@linux.vnet.ibm.com>,
Anton Blanchard <anton@samba.org>,
Michael Ellerman <mpe@ellerman.id.au>,
Ananth N Mavinakayanahalli <ananth@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/3] A few uprobe fixes
Date: Thu, 14 Sep 2017 01:57:59 +0530 [thread overview]
Message-ID: <cover.1505333828.git.naveen.n.rao@linux.vnet.ibm.com> (raw)
The first patch adds a warning if we are unable to install a uprobe
breakpoint and is unchanged from the previous posting at:
https://www.mail-archive.com/linuxppc-dev@lists.ozlabs.org/msg123290.html
The second patch just rate limits the uprobe warnings and is new in this
series.
The third patch fixes how we check for an active uprobe -- we need to
consider if we were actually successful in installing the breakpoint.
This patch is new in this series as well.
- Naveen
Naveen N. Rao (3):
kernel/uprobes: Warn if unable to install breakpoint
kernel/uprobes: Ratelimit messages
kernel/uprobes: Fix check for active uprobe
kernel/events/uprobes.c | 28 +++++++++++++++++++++-------
1 file changed, 21 insertions(+), 7 deletions(-)
--
2.14.1
next reply other threads:[~2017-09-13 20:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-13 20:27 Naveen N. Rao [this message]
2017-09-13 20:28 ` [PATCH v2 1/3] kernel/uprobes: Warn if unable to install breakpoint Naveen N. Rao
2017-09-15 15:53 ` Oleg Nesterov
2017-09-16 11:46 ` Naveen N. Rao
2017-09-13 20:28 ` [PATCH v2 2/3] kernel/uprobes: Ratelimit messages Naveen N. Rao
2017-09-13 20:28 ` [PATCH v2 3/3] kernel/uprobes: Fix check for active uprobe Naveen N. Rao
2017-09-15 15:38 ` Oleg Nesterov
2017-09-16 11:33 ` Naveen N. Rao
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=cover.1505333828.git.naveen.n.rao@linux.vnet.ibm.com \
--to=naveen.n.rao@linux.vnet.ibm.com \
--cc=ananth@linux.vnet.ibm.com \
--cc=anton@samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mpe@ellerman.id.au \
--cc=oleg@redhat.com \
--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