mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@kernel.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: schwidefsky@de.ibm.com, heiko.carstens@de.ibm.com,
	linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC: 2.6 patch] s390: use kernel/uid.c
Date: Fri, 15 Aug 2008 22:00:43 +0300	[thread overview]
Message-ID: <20080815190043.GC1973@cs181140183.pp.htv.fi> (raw)
In-Reply-To: <200808151734.43710.arnd@arndb.de>

On Fri, Aug 15, 2008 at 05:34:43PM +0200, Arnd Bergmann wrote:
> On Sunday 10 August 2008, Adrian Bunk wrote:
> > Unless I missed a twist the only reason for s390 to not use the code in 
> > kernel/uid.c was that it copied the code from sparc64 (that is now 
> > being changed in a similar way by David).
> > 
> > Signed-off-by: Adrian Bunk <bunk@kernel.org>
> 
> I tried doing this before but couldn't figure out an easy way,
> but the circumstances may have changed by now.
> 
> Back then, the basic problem was that CONFIG_UID16 had side-effects
> that break the 64-bit versions of some syscalls. I don't see that
> being the case any more, but from what I can tell, you still need
> to add definitions for __kernel_old_uid_t etc on s390x.

They are already in arch/s390/include/asm/posix_types.h

The one thing I can say about my patch is that it compiles with the 
defconfig (where the uid16 code is used due to COMPAT=y).

> If that does the trick, great work!
> 
> 	Arnd <><

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2008-08-15 19:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-10 20:40 Adrian Bunk
2008-08-15 15:34 ` Arnd Bergmann
2008-08-15 19:00   ` Adrian Bunk [this message]
2008-08-23 13:03     ` Heiko Carstens

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=20080815190043.GC1973@cs181140183.pp.htv.fi \
    --to=bunk@kernel.org \
    --cc=arnd@arndb.de \
    --cc=heiko.carstens@de.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=schwidefsky@de.ibm.com \
    /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

all inboxes | Powered by JetHome®