From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/4] syscall_trace fixes and cleanups
Date: Fri, 15 Jun 2012 16:58:03 +0100 [thread overview]
Message-ID: <1339775887-32103-1-git-send-email-will.deacon@arm.com> (raw)
Hello,
This is version 3 of the patches originally posted here:
v1: http://lists.infradead.org/pipermail/linux-arm-kernel/2012-May/097748.html
v2: http://lists.infradead.org/pipermail/linux-arm-kernel/2012-June/103281.html
The only changes from v2 are that the series is now based on -rc2 and
I've added Al and Eric to CC. Functionally it is identical.
All feedback welcome,
Will
Will Deacon (4):
audit: arm: only allow syscall auditing for pure EABI userspace
ARM: entry: don't bother with syscall tracing on ret_from_fork path
ARM: audit: move syscall auditing until after ptrace SIGTRAP handling
ARM: ptrace: provide separate functions for tracing syscall
{entry,exit}
arch/arm/kernel/entry-common.S | 20 +++++-------------
arch/arm/kernel/ptrace.c | 42 ++++++++++++++++++++++++++++-----------
init/Kconfig | 2 +-
3 files changed, 37 insertions(+), 27 deletions(-)
--
1.7.4.1
next reply other threads:[~2012-06-15 15:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-15 15:58 Will Deacon [this message]
2012-06-15 15:58 ` [PATCH v3 1/4] audit: arm: only allow syscall auditing for pure EABI userspace Will Deacon
2012-06-15 15:58 ` [PATCH v3 2/4] ARM: entry: don't bother with syscall tracing on ret_from_fork path Will Deacon
2012-06-15 15:58 ` [PATCH v3 3/4] ARM: audit: move syscall auditing until after ptrace SIGTRAP handling Will Deacon
2012-06-15 15:58 ` [PATCH v3 4/4] ARM: ptrace: provide separate functions for tracing syscall {entry, exit} Will Deacon
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=1339775887-32103-1-git-send-email-will.deacon@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).