* sys32_rt_sigtimedwait - new question
@ 2004-01-21 16:23 Pavel Kiryukhin
0 siblings, 0 replies; only message in thread
From: Pavel Kiryukhin @ 2004-01-21 16:23 UTC (permalink / raw)
To: linux-mips; +Cc: Pavel Kiryukhin
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2004-01-21 16:20 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-01-21 16:23 sys32_rt_sigtimedwait - new question Pavel Kiryukhin
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.