Return-Path: thread-index: AcQVo/uo4AnpDaJvRwCKMoT6Ow3X+w== Envelope-to: paul@sumlocktest.fsnet.co.uk Delivery-date: Fri, 02 Jan 2004 20:49:33 +0000 Message-ID: <005e01c415a3$fba8c210$d100000a@sbs2003.local> Content-Transfer-Encoding: 7bit Date: Mon, 29 Mar 2004 16:39:11 +0100 From: "Linus Torvalds" X-Mailer: Microsoft CDO for Exchange 2000 To: Cc: , , , , Subject: Re: siginfo_t fracturing, especially for 64/32-bit compatibility mode In-Reply-To: <20040102203820.GA3147@rudolph.ccur.com> Content-Class: urn:content-classes:message References: <20040102194909.GA2990@rudolph.ccur.com> <20040102203820.GA3147@rudolph.ccur.com> Importance: normal Priority: normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset="US-ASCII" Sender: X-Mailing-List: linux-kernel@vger.kernel.org X-OriginalArrivalTime: 29 Mar 2004 15:39:13.0859 (UTC) FILETIME=[FCD07930:01C415A3] 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 - 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/