linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 0/8] Fix restart_block syscall restarting for 3.5
Date: Fri, 22 Jun 2012 16:06:58 +0100	[thread overview]
Message-ID: <1340377626-17075-1-git-send-email-will.deacon@arm.com> (raw)

Hello,

This RFC series attempts to address the syscall restarting problems
introduced during the merge window and described here:

  http://lists.infradead.org/pipermail/linux-arm-kernel/2012-June/104733.html

I reckon the first two reverts should go in for 3.5 unless anybody has
a better solution. The rest of the code is an RFC since, as Russell has
said before, the code is `rather yucky'.

In my effort to avoid breaking strace, I ended up merging in my audit
fixes with this series since keeping the patch sets separate was
becoming a bit of a nightmare given the amount of common code they are
modifying.

Given the mysterious ability of this code to wrap my brain around my
face and beat it with a hammer, I would really appreciate some feedback!

Cheers,

Will


Will Deacon (8):
  Revert "arm: remove unused restart trampoline"
  Revert "arm: new way of handling ERESTART_RESTARTBLOCK"
  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}
  ARM: signal: perform restart_block system call restarting in the
    kernel
  Revert "Revert "arm: remove unused restart trampoline""

 arch/arm/include/asm/ptrace.h      |    3 ++
 arch/arm/include/asm/thread_info.h |   11 +++---
 arch/arm/kernel/calls.S            |    2 +-
 arch/arm/kernel/entry-common.S     |   25 ++++++--------
 arch/arm/kernel/ptrace.c           |   37 +++++++++++++-------
 arch/arm/kernel/signal.c           |   63 ++++++++++++++++++++++++------------
 init/Kconfig                       |    2 +-
 7 files changed, 88 insertions(+), 55 deletions(-)

-- 
1.7.4.1

             reply	other threads:[~2012-06-22 15:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-22 15:06 Will Deacon [this message]
2012-06-22 15:06 ` [RFC PATCH 1/8] Revert "arm: remove unused restart trampoline" Will Deacon
2012-06-22 15:07 ` [RFC PATCH 2/8] Revert "arm: new way of handling ERESTART_RESTARTBLOCK" Will Deacon
2012-06-22 15:07 ` [RFC PATCH 3/8] audit: arm: only allow syscall auditing for pure EABI userspace Will Deacon
2012-06-22 15:07 ` [RFC PATCH 4/8] ARM: entry: don't bother with syscall tracing on ret_from_fork path Will Deacon
2012-06-22 15:07 ` [RFC PATCH 5/8] ARM: audit: move syscall auditing until after ptrace SIGTRAP handling Will Deacon
2012-06-22 15:07 ` [RFC PATCH 6/8] ARM: ptrace: provide separate functions for tracing syscall {entry, exit} Will Deacon
2012-06-22 15:07 ` [RFC PATCH 7/8] ARM: signal: perform restart_block system call restarting in the kernel Will Deacon
2012-06-22 15:07 ` [RFC PATCH 8/8] Revert "Revert "arm: remove unused restart trampoline"" Will Deacon
2012-06-22 19:36 ` [RFC PATCH 0/8] Fix restart_block syscall restarting for 3.5 Al Viro
2012-06-25  9:18   ` Will Deacon
2012-06-26 14:33     ` 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=1340377626-17075-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).