mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Linus Torvalds" <torvalds@osdl.org>
To: <Administrator@smtp.paston.co.uk>
Cc: <akpm@osdl.org>, <ak@suse.de>, <linux-kernel@vger.kernel.org>,
	<albert.cahalan@ccur.com>, <jim.houston@ccur.com>
Subject: Re: siginfo_t fracturing, especially for 64/32-bit compatibility mode
Date: Mon, 29 Mar 2004 16:39:11 +0100	[thread overview]
Message-ID: <005e01c415a3$fba8c210$d100000a@sbs2003.local> (raw)
In-Reply-To: <20040102203820.GA3147@rudolph.ccur.com>



On Fri, 2 Jan 2004, Joe Korty wrote:
>
> Indeed we do, and that is the problem.  32 bit apps by definition use
> the 32 bit version of siginfo_t and the first act the kernel has to do
> on receiving one of these is convert it to 64 bit for consumption by
> the rest of the kernel.  In order to do that, the kernel must know what
> fields in siginfo_t the user has set.

Ahh, a light goes on. Yeah, that's broken. Argh.

		Linus

  parent reply	other threads:[~2004-03-29 15:39 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-02 19:49 Joe Korty
2004-01-02 20:28 ` Linus Torvalds
2004-01-02 20:38   ` Joe Korty
2004-01-02 20:47     ` Linus Torvalds
2004-03-29 15:39     ` Linus Torvalds [this message]
2004-03-29 15:39   ` Joe Korty
2004-01-03  0:24 ` Andi Kleen
2004-01-03  0:44   ` Jakub Jelinek
2004-01-03  1:07     ` Andi Kleen
2004-01-03  2:12       ` Daniel Jacobowitz
2004-03-29 15:39       ` Daniel Jacobowitz
2004-03-29 15:39     ` Andi Kleen
2004-01-03 20:15   ` Joe Korty
2004-03-29 15:39   ` Jakub Jelinek
2004-03-29 15:40   ` Joe Korty
2004-03-29 15:39 ` Linus Torvalds
2004-03-29 15:39 ` Andi Kleen

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='005e01c415a3$fba8c210$d100000a@sbs2003.local' \
    --to=torvalds@osdl.org \
    --cc=Administrator@smtp.paston.co.uk \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=albert.cahalan@ccur.com \
    --cc=jim.houston@ccur.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

Powered by JetHome