All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Maxim Kuvyrkov <maxim@codesourcery.com>
Cc: Andreas Schwab <schwab@linux-m68k.org>, linux-m68k@vger.kernel.org
Subject: Re: [PATCH] Fix siginfo._uid bug
Date: Wed, 23 Dec 2009 19:37:27 +0100	[thread overview]
Message-ID: <10f740e80912231037ua8724f4s8965b5c5b255ddfd@mail.gmail.com> (raw)
In-Reply-To: <10f740e80911240501v238f023ahcdab0c1fe8600bf5@mail.gmail.com>

On Tue, Nov 24, 2009 at 14:01, Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> On Thu, Nov 19, 2009 at 20:47, Maxim Kuvyrkov <maxim@codesourcery.com> wrote:
>> Geert Uytterhoeven wrote:
>>> On Mon, Oct 26, 2009 at 15:21, Maxim Kuvyrkov <maxim@codesourcery.com>
>>> wrote:
>>>>
>>>> Maxim Kuvyrkov wrote:
>>>>>
>>>>> Maxim Kuvyrkov wrote:
>>>>>>
>>>>>> Andreas Schwab wrote:
>>
>> ...
>>>>>>
>>>>>> 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?
>>>
>>> Unfortunately I'm far from a signal expert...
>>>
>>> Fixing this breaks backwards compatibility, right?
>>
>> Not really.  Fixing this bug will only make applications to receive expected
>> results in signal handlers they register.
>>
>>> So what are the consequences? Which applications are affected? Just
>>> gdb? So we need a fixed gdb binary in Debian?
>>
>> While GDB is a heavy user of signals, it's not the only application that's
>> affected.  GLIBC is affected for sure, as is anything that is using signals
>> to the extent of checking UID of the process which sent the signal.
>>
>> The question is which solution should we adopt.  The patch I posted fixes
>> all current problems with have on our hands.  Andreas suggested to move to
>> the generic layout of `struct siginfo' which will make future problems less
>> likely, but this approach may need additional investigation.
>
> If moving to the generic layout decreases the probability of future problems,
> it's the way to go.

Do we have a patch somewhere?

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds

  reply	other threads:[~2009-12-23 18:37 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
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 [this message]
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=10f740e80912231037ua8724f4s8965b5c5b255ddfd@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=maxim@codesourcery.com \
    --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.