Messages in this thread | | | Date | Fri, 2 Jan 2004 21:12:47 -0500 | From | Daniel Jacobowitz <> | Subject | Re: siginfo_t fracturing, especially for 64/32-bit compatibility mode |
| |
On Sat, Jan 03, 2004 at 02:07:26AM +0100, Andi Kleen wrote: > On Fri, 2 Jan 2004 19:44:06 -0500 > Jakub Jelinek <jakub@redhat.com> 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/
| |