Date: Fri, 2 Jan 2004 15:38:21 -0500
From: Joe Korty <joe.korty@ccur.com>
To: Linus Torvalds <torvalds@osdl.org>
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
Message-ID: <20040102203820.GA3147@rudolph.ccur.com>
Reply-To: Joe Korty <joe.korty@ccur.com>
References: <20040102194909.GA2990@rudolph.ccur.com> <Pine.LNX.4.58.0401021226150.5282@home.osdl.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.58.0401021226150.5282@home.osdl.org>
User-Agent: Mutt/1.4i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 871
Lines: 22

[ resend, accidently sent originally from a broken email account ]

> On Fri, 2 Jan 2004, Joe Korty wrote:
>> siginfo_t processing is fragile when in 32 bit compatibility mode on
>> a 64 bit processor.
> 
> It shouldn't be.
> Inside the kernel, we should always use the "native" format (ie 64-bit). 

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.

Joe

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/