linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Christoph Hellwig <hch@lst.de>,
	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:34:43 +0100	[thread overview]
Message-ID: <20100108153443.GA14494@lst.de> (raw)
In-Reply-To: <201001081157.17195.arnd@arndb.de>

On Fri, Jan 08, 2010 at 11:57:17AM +0100, Arnd Bergmann wrote:
> > Add a generic implementation of the ipc demultiplexer syscall.  Except for
> > s390 and sparc64 all implementations of the sys_ipc are nearly identical.
> 
> I think the s390 version is trivial to add as well, like
> 
> SYSCALL_DEFINE5(s390_ipc, uint, call, int, first, unsigned long, second,
>  		unsigned long, third, void __user *, ptr)
> {
> 	if (call == SEMTIMEDOP)
> 		return sys_semtimedop(first, (struct sembuf __user *)ptr,
> 				      (unsigned) second,
> 				      (const struct timespec __user *)third);
> 
> 	return sys_ipc(call & 0xffff, first, second, third, ptr, 0);
> }

Possiblly.  Not sure if it's worth it, though.  If the s390 maintainers
want it I'd say do it as a separate patch.

> But while going over the code again, I noticed that you broke sign extension
> 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?

> This is needed to make sure the upper half of the register is filled with
> zero-extended or sign-extended correctly and does not contain random garbage
> in the native 64 bit case. IIRC, x86_64 does not have this problem and mips64
> may have the wrong code already. Alpha, parisc and ia64 don't have a native
> sys_ipc and the rest are 32 bit, so they don't care.

I can fix it up, but I don't quite understand the need.

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

Thread overview: 16+ 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 17:21 ` 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 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 [this message]
2010-01-08 15:49         ` Arnd Bergmann
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=20100108153443.GA14494@lst.de \
    --to=hch@lst.de \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=benh@kernel.crashing.org \
    --cc=davem@davemloft.net \
    --cc=dhowells@redhat.com \
    --cc=geert@linux-m68k.org \
    --cc=gerg@uclinux.org \
    --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;
as well as URLs for NNTP newsgroup(s).