linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: viro@ZenIV.linux.org.uk (Al Viro)
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 20:36:26 +0100	[thread overview]
Message-ID: <20120622193626.GG14083@ZenIV.linux.org.uk> (raw)
In-Reply-To: <1340377626-17075-1-git-send-email-will.deacon@arm.com>

On Fri, Jun 22, 2012 at 04:06:58PM +0100, Will Deacon wrote:
> 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'.

See commit 76c3f4da3ee47b68304dbe0f64e86562e7945bf3 and a couiple before it in
signal.git:
commit 76c3f4da3ee47b68304dbe0f64e86562e7945bf3
Author: Al Viro <viro@zeniv.linux.org.uk>
Date:   Sat Jun 2 02:11:01 2012 -0400

    arm: get rid of TIF_SYSCALL_RESTARTSYS
    
    just let do_work_pending() return 1 on normal local restarts and
    -1 on those that had been caused by ERESTART_RESTARTBLOCK (and 0
    is still "all done, sod off to userland now").  And let the asm
    glue flip scno to restart_syscall(2) one if it got negative from
    us...
    
    Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>

commit 9c802c169f964830496be6480ab71d2123cf38a7
Author: Al Viro <viro@zeniv.linux.org.uk>
Date:   Sat Jun 2 01:52:18 2012 -0400

    arm: deal with handlerless restarts without leaving the kernel
    
    Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>

commit c1eafa6fc84aaf725e02c7b50ee8a8a748f45b63
Author: Al Viro <viro@zeniv.linux.org.uk>
Date:   Fri Jun 1 23:58:57 2012 -0400

    arm: pull all work_pending logics into C function
    
    Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>

  parent reply	other threads:[~2012-06-22 19:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-22 15:06 [RFC PATCH 0/8] Fix restart_block syscall restarting for 3.5 Will Deacon
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 ` Al Viro [this message]
2012-06-25  9:18   ` [RFC PATCH 0/8] Fix restart_block syscall restarting for 3.5 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=20120622193626.GG14083@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --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).