All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maxim Kuvyrkov <maxim@codesourcery.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>, linux-m68k@vger.kernel.org
Subject: Re: [PATCH] Fix siginfo._uid bug
Date: Wed, 16 Sep 2009 23:56:06 +0400	[thread overview]
Message-ID: <4AB142D6.3050602@codesourcery.com> (raw)
In-Reply-To: <m21vm6k76e.fsf@igel.home>

Andreas Schwab wrote:
> Maxim Kuvyrkov <maxim@codesourcery.com> writes:
> 
>> The bug is rather elegant and has been present in sources for years.
> 
> For more than 9 years, to be precise, when 32 bit uids were introduced.
> 
>> The problem is that m68k uses a custom siginfo layout due to having
>> a 16-bit uid field for 'backward compatibility'.  I.e., siginfo._kill
>> fields are:
> 
> I've found this interesting thread from 2000:
> 
> http://marc.info/?l=linux-kernel&m=94829131029274&w=2
> 
> The change went in 2.3.41, and undid the change made in 2.3.39.  It was
> reintroduced (for asm-m68k/siginfo.h only and with __kernel_* types; no
> other siginfo header used them at that time) in 2.4.0-test12.
> 
> Now looking at the glibc side, m68k has always used the generic
> linux/bits/siginfo.h (with a single 32bit uid field), until Richard
> Sandiford introduced linux/m68k/siginfo.h in October 2006, copying the
> (broken) layout from the kernel.
> 
> Given that there is no way to keep backward compatibility it might be a
> good opportunity to do same cleanup here.  Like going back to the
> generic layout.

I can only cheer for going to the generic layout as I don't want repeat 
the exercise of hunting a bug that is both in the kernel and glibc.

--
Maxim

  reply	other threads:[~2009-09-16 19:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-16 16:35 [PATCH] Fix siginfo._uid bug Maxim Kuvyrkov
2009-09-16 19:42 ` Andreas Schwab
2009-09-16 19:56   ` Maxim Kuvyrkov [this message]
2009-09-18 15:18   ` Maxim Kuvyrkov
2009-10-02  8:54     ` Maxim Kuvyrkov
2009-10-26 14:21       ` Maxim Kuvyrkov
2009-11-19 19:31         ` Geert Uytterhoeven
2009-11-19 19:47           ` Maxim Kuvyrkov
2009-11-24 13:01             ` Geert Uytterhoeven
2009-12-23 18:37               ` Geert Uytterhoeven
2009-12-23 19:47                 ` Maxim Kuvyrkov
2010-01-08 19:32                   ` Geert Uytterhoeven

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=4AB142D6.3050602@codesourcery.com \
    --to=maxim@codesourcery.com \
    --cc=geert@linux-m68k.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=schwab@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 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.