public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Christoph Hellwig <hch@lst.de>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
	linux-arch@vger.kernel.org, linux@arm.linux.org.uk,
	starvik@axis.com, jesper.nilsson@axis.com, dhowells@redhat.com,
	ysato@users.sourceforge.jp, takata@linux-m32r.org,
	geert@linux-m68k.org, zippel@linux-m68k.org, gerg@uclinux.org,
	ralf@linux-mips.org, benh@kernel.crashing.org,
	schwidefsky@de.ibm.com, heiko.carstens@de.ibm.com,
	lethal@linux-sh.org, davem@davemloft.net, jdike@addtoit.com,
	tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
	viro@zeniv.linux.org.uk
Subject: Re: [PATCH v3 3/3] generic sys_ipc wrapper
Date: Fri, 8 Jan 2010 16:49:34 +0100	[thread overview]
Message-ID: <201001081649.34308.arnd@arndb.de> (raw)
In-Reply-To: <20100108153443.GA14494@lst.de>

On Friday 08 January 2010, Christoph Hellwig wrote:
> Possiblly.  Not sure if it's worth it, though.  If the s390 maintainers
> want it I'd say do it as a separate patch.

Sounds fair.

> at least on powerpc and s390, possibly on all 64 bit machines:
> 
> > > +                   return -EINVAL;
> > > +           if (get_user(fourth.__pad, (void __user * __user *) ptr))
> > > +                   return -EFAULT;
> > > +           return sys_semctl(first, second, third, fourth);
> > 
> >               return sys_semctl(first, (int)second, third, fourth);
> 
> What does the explicit case buy us in terms of sign-extension over
> the implicit one given that the second argument to sys_semctl already is
> types as int?

You're right, it's not needed any more, in particular since Heiko
added the wrappers around each syscall to do yet another sign extension,
but this one was probably right in your version already.

You convinced me that the patch is good in its current shape.

Acked-by: Arnd Bergmann <arnd@arndb.de>

	Arnd

  reply	other threads:[~2010-01-08 15:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-06 17:21 [PATCH 3/3] generic sys_ipc wrapper Christoph Hellwig
2010-01-06 18:22 ` Al Viro
2010-01-06 19:16 ` David Howells
2010-01-06 19:52 ` Arnd Bergmann
2010-01-06 19:59   ` Russell King - ARM Linux
2010-01-06 20:48     ` Arnd Bergmann
2010-01-06 22:33 ` Heiko Carstens
2010-01-08  9:50 ` [PATCH v2 " Christoph Hellwig
2010-01-08 10:03   ` [PATCH v3 " Christoph Hellwig
2010-01-08 10:57     ` Arnd Bergmann
2010-01-08 15:34       ` Christoph Hellwig
2010-01-08 15:49         ` Arnd Bergmann [this message]
2010-01-10  4:51     ` Al Viro
2010-01-14 15:25     ` David Howells

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=201001081649.34308.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=akpm@linux-foundation.org \
    --cc=benh@kernel.crashing.org \
    --cc=davem@davemloft.net \
    --cc=dhowells@redhat.com \
    --cc=geert@linux-m68k.org \
    --cc=gerg@uclinux.org \
    --cc=hch@lst.de \
    --cc=heiko.carstens@de.ibm.com \
    --cc=hpa@zytor.com \
    --cc=jdike@addtoit.com \
    --cc=jesper.nilsson@axis.com \
    --cc=lethal@linux-sh.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=mingo@redhat.com \
    --cc=ralf@linux-mips.org \
    --cc=schwidefsky@de.ibm.com \
    --cc=starvik@axis.com \
    --cc=takata@linux-m32r.org \
    --cc=tglx@linutronix.de \
    --cc=viro@zeniv.linux.org.uk \
    --cc=ysato@users.sourceforge.jp \
    --cc=zippel@linux-m68k.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