public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@ZenIV.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Nicolas Dichtel <nicolas.dichtel@6wind.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Issues with "x86, um: switch to generic fork/vfork/clone" commit
Date: Sun, 20 Jan 2013 21:28:32 +0000	[thread overview]
Message-ID: <20130120212832.GP4939@ZenIV.linux.org.uk> (raw)
In-Reply-To: <CA+55aFyRMC43_H1hL5goAQxX4EdTuXOu5A9CoBk9fpGoJT_nig@mail.gmail.com>

On Sun, Jan 20, 2013 at 12:53:20PM -0800, Linus Torvalds wrote:
> On Sat, Jan 19, 2013 at 7:12 PM, Al Viro <viro@zeniv.linux.org.uk> wrote:
> >
> > OK...  I think I understand what's going on.  We need asmlinkage_protect
> > in sys_clone() ;-/  For what it's worth, I really wonder if we ought to
> > treat that as syscall wrappers - i.e. have SYSCALL_DEFINEx on i386 add
> > a wrapper that would do asmlinkage_protect itself.  IMO it's the same kind
> > of thing as argument normalization handled by syscall wrappers - we make
> > sure that C function plays well with what asm glue is doing and expecting.
> 
> Actually, I think we should do it *unconditionally* in the syscall wrappers.

That's what I mean; sorry for bad wording - should be "use SYSCALL_DEFINEx on
i386, adding a wrapper that would do asmlinkage_protect".  And yes, i386 is
the only architecture that currently has a non-empty asmlinkage_protect(),
so all architecture dependencies would already be taken care of -
SYSCALL_DEFINEx should use asmlinkage_protect() unconditionally.

> But in the meantime, I guess I should just take the do_fork() one. Can
> I get a sign-off and a changelog?

See signal.git#for-linus; regression fixes (including this one) +
compat syscall fixes (discussed back in December) + a couple of "make
life easier for sigaltstack stuff by reducing inter-tree dependencies"
Please, pull from the usual place
git://git.kernel.org/pub/scm/linux/kernel/git/viro/signal for-linus

Shortlog:
Al Viro (6):
      switch compat_sys_sigaltstack() to COMPAT_SYSCALL_DEFINE
      switch compat_sys_wait4() and compat_sys_waitid() to COMPAT_SYSCALL_DEFINE
      x32: fix waitid()
      x32: fix sigtimedwait
      make sure that /linuxrc has std{in,out,err}
      sys_clone() needs asmlinkage_protect

Vineet Gupta (2):
      Ensure that kernel_init_freeable() is not inlined into non __init code
      CONFIG_GENERIC_SIGALTSTACK build breakage with asm-generic/syscalls.h

Diffstat:
 include/asm-generic/syscalls.h |    2 ++
 init/do_mounts_initrd.c        |    4 ++++
 init/main.c                    |    4 ++--
 kernel/compat.c                |   23 +++++++++++++++--------
 kernel/fork.c                  |    6 ++++--
 kernel/signal.c                |    5 +++--
 6 files changed, 30 insertions(+), 14 deletions(-)


  reply	other threads:[~2013-01-20 21:28 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-14  9:42 Issues with "x86, um: switch to generic fork/vfork/clone" commit Nicolas Dichtel
2013-01-19  6:38 ` Al Viro
2013-01-20  3:12   ` Al Viro
2013-01-20 20:53     ` Linus Torvalds
2013-01-20 21:28       ` Al Viro [this message]
2013-01-21  1:22       ` Al Viro
2013-01-21  1:40         ` Linus Torvalds
2013-01-21  2:30           ` Al Viro
2013-01-21  2:39             ` Linus Torvalds
2013-01-21  6:02               ` Al Viro
2013-01-21 22:55             ` [RFC] making HAVE_SYSCALL_WRAPPERS universal (Re: Issues with "x86, um: switch to generic fork/vfork/clone" commit) Al Viro
2013-01-22 12:47               ` James Hogan
2013-01-22 14:23                 ` Al Viro
2013-01-22 13:16               ` Arnd Bergmann
2013-01-22 15:33               ` Arnd Bergmann
2013-01-21  9:00     ` Issues with "x86, um: switch to generic fork/vfork/clone" commit Nicolas Dichtel
  -- strict thread matches above, loose matches on Subject: below --
2012-11-10  4:36 Michel Lespinasse
2012-11-10  4:51 ` Al Viro
2012-11-10  4:57   ` Michel Lespinasse
2012-11-10  5:33     ` Al Viro
2012-11-10  5:47       ` Michel Lespinasse
2012-11-10  7:33         ` Al Viro
2012-11-10  8:08           ` Michel Lespinasse
2012-11-10 18:59           ` Al Viro

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=20130120212832.GP4939@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nicolas.dichtel@6wind.com \
    --cc=torvalds@linux-foundation.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