From: Pavel Kiryukhin <savl@dev.rtsoft.ru>
To: linux-mips@linux-mips.org
Cc: Pavel Kiryukhin <savl@dev.rtsoft.ru>
Subject: sys32_rt_sigtimedwait - new question
Date: Wed, 21 Jan 2004 19:23:49 +0300 [thread overview]
Message-ID: <400EA795.3030200@dev.rtsoft.ru> (raw)
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
reply other threads:[~2004-01-21 16:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=400EA795.3030200@dev.rtsoft.ru \
--to=savl@dev.rtsoft.ru \
--cc=linux-mips@linux-mips.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox