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 _at_ vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
References:
- siginfo_t fracturing, especially for 64/32-bit compatibility modeJoe Korty
- Re: siginfo_t fracturing, especially for 64/32-bit compatibilitymodeLinus Torvalds
- Re: siginfo_t fracturing, especially for 64/32-bit compatibility modeJoe Korty
- Prev by Date: Re: udev and devfs - The final word
- Next by Date: Re: [PATCH] 2.6.0 batch scheduling, HT aware
- Previous by thread: Re: siginfo_t fracturing, especially for 64/32-bit compatibility mode
- Next by thread: Re: siginfo_t fracturing, especially for 64/32-bit compatibilitymode
- Indexes:[Main][Thread]