Messages in this thread | | | Date | Thu, 08 Mar 2007 15:57:38 -0800 | From | Jeremy Fitzhardinge <> | Subject | Re: [patch 2/5] signalfd v2 - signalfd core ... |
| |
Linus Torvalds wrote: > So I think you should get rid of signalfd_dequeue(), and just replace it > with a "read()" function. >
The difficulty is that there are 4 different formats of signal structure you could get: (traditional|siginfo) x (32bit|64bit).
What happens if you're a 32 bit process, you fork and exec a 64bit process who inherits the signalfd, and they start reading? What format of signal structure do they get? What do you get? What if you start doing partial reads?
I think signalfd_dequeue() is warty, but read() has has a number of details to sort out.
(Hey, can you send signals by writing into the signalfd? Very plan9...)
J - 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/
| |