public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Maxim Kuvyrkov <maxim@codesourcery.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Andreas Schwab <schwab@linux-m68k.org>, linux-m68k@vger.kernel.org
Subject: Re: [PATCH] Fix siginfo._uid bug
Date: Mon, 26 Oct 2009 17:21:32 +0300	[thread overview]
Message-ID: <4AE5B06C.1090303@codesourcery.com> (raw)
In-Reply-To: <4AC5BFA8.4040805@codesourcery.com>

Maxim Kuvyrkov wrote:
> Maxim Kuvyrkov wrote:
>> 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.
> ...
>>> 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.
>>
>> There is yet another bug in siginfo.  si_sigval is expected to be at 
>> the same offsets in _timer and _rt.  At the moment si_sigval is at 
>> offset 8 in _timer and at offset 6 in _rt (the patch for fixing uids 
>> makes that 8@_timer and 10@_rt).
>>
>> This bug causes rt/tst-*timer* tests fail.
>>
>> Moving on to the generic version of siginfo.h will certainly fix the 
>> problem, otherwise, one needs to pad extra 2 bytes in _timer.
> 
> While the discussion is pending, here is an updated version of the patch 
> that also patches up sigval.

Ping?  Broken signal handling is a quite serious bug.

Geert, which option of fixing would you prefer?

-- 
Maxim Kuvyrkov
CodeSourcery
maxim@codesourcery.com
(650) 331-3385 x724

  reply	other threads:[~2009-10-26 14:28 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
2009-09-18 15:18   ` Maxim Kuvyrkov
2009-10-02  8:54     ` Maxim Kuvyrkov
2009-10-26 14:21       ` Maxim Kuvyrkov [this message]
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=4AE5B06C.1090303@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox