linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Ulrich Weigand <Ulrich.Weigand@de.ibm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: sizeof (siginfo_t) problem
Date: Mon, 14 Jul 2003 14:35:59 -0400	[thread overview]
Message-ID: <20030714143558.P15481@devserv.devel.redhat.com> (raw)
In-Reply-To: <OF8354A4F2.09CC83D0-ONC1256D63.0064A671@de.ibm.com>; from Ulrich.Weigand@de.ibm.com on Mon, Jul 14, 2003 at 08:31:34PM +0200

On Mon, Jul 14, 2003 at 08:31:34PM +0200, Ulrich Weigand wrote:
> The MD_FALLBACK_FRAME_STATE_FOR macro does not use sizeof(siginfo_t)
> at all, but hardcodes 128.  (This has always been the case, and was
> done to avoid the need to include signal.h.)  This is still broken
> with the current kernel behaviour, though.
> 
> It is strange that I didn't notice the problem earlier; apparently
> most of the places where unwinding through signal frames is required
> use non-RT frames ...

But it is crucial for NPTL pthread_cancel.

> >This though means that the kernel siginfo_t change cannot be done
> >just in asm-*/siginfo.h headers - at least places where siginfo_t
> >is present within some structures ever visible to userland a dummy
> >8 byte pad needs to be inserted.
> 
> As userspace expects a size of 128 bytes, and with the change
> the size now *is* 128 bytes, why would a pad be required?

As I tried to write, we either can have all GCCs
which will work properly only with new kernels (no pad added),
or we can have new GCCs working with all kernels (if pad is added).
Your choice...

	Jakub

  reply	other threads:[~2003-07-14 18:21 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-14 18:31 sizeof (siginfo_t) problem Ulrich Weigand
2003-07-14 18:35 ` Jakub Jelinek [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-07-15 11:58 Martin Schwidefsky
2003-07-14 18:52 Ulrich Weigand
2003-07-14 12:40 Jakub Jelinek
2003-07-14 13:55 ` Jamie Lokier
2003-07-14 15:02   ` Andreas Schwab
2003-07-14 15:48 ` David Mosberger
2003-07-14 15:57   ` Jakub Jelinek
2003-07-14 16:52 ` Stephen Rothwell
2003-07-14 17:00   ` Jakub Jelinek
2003-07-14 17:11     ` Stephen Rothwell
2003-07-14 17:14       ` Jakub Jelinek
2003-07-14 17:25         ` Stephen Rothwell
2003-07-14 17:45           ` Jakub Jelinek
2003-07-19 18:32   ` Anton Blanchard
2003-07-21  0:08     ` Stephen Rothwell
2003-07-22 13:42       ` Russell King
2003-07-22 13:57         ` Stephen Rothwell

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=20030714143558.P15481@devserv.devel.redhat.com \
    --to=jakub@redhat.com \
    --cc=Ulrich.Weigand@de.ibm.com \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).