linux-mips
[Top] [All Lists]

sys32_rt_sigtimedwait - new question

To: linux-mips@linux-mips.org
Subject: sys32_rt_sigtimedwait - new question
From: Pavel Kiryukhin <savl@dev.rtsoft.ru>
Date: Wed, 21 Jan 2004 19:23:49 +0300
Cc: Pavel Kiryukhin <savl@dev.rtsoft.ru>
Original-recipient: rfc822;linux-mips@linux-mips.org
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624
Hi,
concerning endiannes checking in sys32_rt_sigtimedwait:
just let me note that we have get_sigset and put_sigset that are used in sys32_rt_[sigaction, sigprocmask, sigpending ...] in signal32.c. Thise functions does not use endian check. Don't know if we can use get_sigset in sys32_rt_sigtimedwait.

But I have another question about sys32_rt_sigtimedwait:
We can see the comment about "brainfarting competition". Based on this comment only part of sigset is copied from user space to kernel. Why signals greater than 64 should not be handled? If we look at sys32_rt_sigtimedwait in ppc64/kernel/signal32.c or sparc64/sys_sparc32.c we can see that full sigset (compat_sigset_t) is copied from user while in mips compat_old_sigset is copied. Why it is different in MIPS?
-------
Regards
Pavel Kiryukhin



<Prev in Thread] Current Thread [Next in Thread>
  • sys32_rt_sigtimedwait - new question, Pavel Kiryukhin <=