Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S265793AbUACCNX (ORCPT ); Fri, 2 Jan 2004 21:13:23 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S265886AbUACCNX (ORCPT ); Fri, 2 Jan 2004 21:13:23 -0500 Received: from nevyn.them.org ([66.93.172.17]:14275 "EHLO nevyn.them.org") by vger.kernel.org with ESMTP id S265793AbUACCMy (ORCPT ); Fri, 2 Jan 2004 21:12:54 -0500 Date: Fri, 2 Jan 2004 21:12:47 -0500 From: Daniel Jacobowitz To: Andi Kleen Cc: Jakub Jelinek , joe.korty@ccur.com, akpm@osdl.org, torvalds@osdl.org, 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: <20040103021247.GA29565@nevyn.them.org> Mail-Followup-To: Andi Kleen , Jakub Jelinek , joe.korty@ccur.com, akpm@osdl.org, torvalds@osdl.org, linux-kernel@vger.kernel.org, albert.cahalan@ccur.com, jim.houston@ccur.com References: <20040102194909.GA2990@rudolph.ccur.com> <20040103012433.6aa4cafb.ak@suse.de> <20040103004406.GA24876@devserv.devel.redhat.com> <20040103020726.7c4397bc.ak@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040103020726.7c4397bc.ak@suse.de> User-Agent: Mutt/1.5.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1201 Lines: 28 On Sat, Jan 03, 2004 at 02:07:26AM +0100, Andi Kleen wrote: > On Fri, 2 Jan 2004 19:44:06 -0500 > Jakub Jelinek wrote: > > > On Sat, Jan 03, 2004 at 01:24:33AM +0100, Andi Kleen wrote: > > > > rt_sigqueueinfo(2) subverts this by reserving a range of si_code > > > > values for users, and there is nothing about them to indicate to the > > > > kernel which fields of siginfo_t are actually in use. This is not a > > > > > > My understanding was that the syscall always only supports si_int/si_ptr. > > > > No, why? > > Because otherwise it cannot be supported in the 32bit emulation. Or rather you > won't get any conversion. That's probably an acceptable limitation I think what the OP pointed out is that they _are_ converted, from 32-bit to 64-bit, when a 32-bit process sends a siginfo to another 32-bit process, thereby garbling it. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer - 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/