All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tim Hockin <thockin@sun.com>
To: Tim Hockin <thockin@sun.com>
Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>,
	linux-390@vm.marist.edu,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH} s390x sys32 duplicated code cleanup (was [PATCH RFC] s390x sys32...)
Date: Wed, 04 Sep 2002 11:19:51 -0700	[thread overview]
Message-ID: <3D764EC7.2040306@sun.com> (raw)
In-Reply-To: 3D6D6DDA.5080907@sun.com

Tim Hockin wrote:
> Martin Schwidefsky wrote:
> 
>>> It seems to me that if we do:
>>> * s390x defines CONFIG_UID16
>>> * typedef __kernel_old_gid_t to u16
>>> * get rid of all the sys32_*16 stuff and just call the uid16.c function
>>
>>
>> I checked the code and didn't find any reason why this shouldn't work.
>> In fact with the 31 bit emulation layer the 64 bit kernel does need the
>> 16 bit uid/gid system calls although only for the emulation. To make it
>> really perfect you could define CONFIG_UID16 dependent on
>> CONFIG_S390_SUPPORT. This saves a few bytes in the image if the emulation
>> support is not enabled.

Uggh, DaveM pointed out a very good issue with this fix (similar for 
Sparc64) and core files.  Core files will now have truncated uid/gid 
values because fs/binfmt_elf calls NEW_TO_OLD_UID().  May be other 
places, too.

I guess you should not apply this patch until I've had a better think 
about it.

Tim




-- 
Tim Hockin
Systems Software Engineer
Sun Microsystems, Linux Kernel Engineering
thockin@sun.com


  reply	other threads:[~2002-09-04 18:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-27  7:29 [PATCH RFC] s390x sys32 (remove duplicated code) Martin Schwidefsky
2002-08-29  0:42 ` [PATCH} s390x sys32 duplicated code cleanup (was [PATCH RFC] s390x sys32...) Tim Hockin
2002-09-04 18:19   ` Tim Hockin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-09-05  7:30 Martin Schwidefsky

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=3D764EC7.2040306@sun.com \
    --to=thockin@sun.com \
    --cc=linux-390@vm.marist.edu \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.