From: Davide Libenzi <davidel@xmailserver.org>
To: Ulrich Drepper <drepper@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: [patch 0/6] sys_indirect RFC - sys_indirect introduction
Date: Sat, 30 Jun 2007 15:32:33 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0706301529310.2957@alien.or.mcafeemobile.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0706301458300.2957@alien.or.mcafeemobile.com>
On Sat, 30 Jun 2007, Davide Libenzi wrote:
> Think about if we had this for the latest pselect/ppoll/epoll_pwait.
> Think about how your solution and mine would apply to that very much
> concrete case.
This is how all those overloaded syscalls looks like, BTW:
if (sigmask) {
if (sigsetsize != sizeof(sigset_t))
return -EINVAL;
if (copy_from_user(&ksigmask, sigmask, sizeof(ksigmask)))
return -EFAULT;
sigdelsetmask(&ksigmask, sigmask(SIGKILL) | sigmask(SIGSTOP));
sigprocmask(SIG_SETMASK, &ksigmask, &sigsaved);
}
error = sys_XXX(...);
if (sigmask) {
if (error == -EINTR) {
memcpy(¤t->saved_sigmask, &sigsaved,
sizeof(sigsaved));
set_thread_flag(TIF_RESTORE_SIGMASK);
} else
sigprocmask(SIG_SETMASK, &sigsaved, NULL);
}
How would you do that with a single shared strcture, w/out adding in all
signal paths the knowledge of the structure?
- Davide
next prev parent reply other threads:[~2007-06-30 22:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-29 21:48 Davide Libenzi
2007-06-30 1:48 ` Ulrich Drepper
2007-06-30 19:23 ` Davide Libenzi
2007-06-30 21:54 ` Ulrich Drepper
2007-06-30 22:27 ` Davide Libenzi
2007-06-30 22:32 ` Davide Libenzi [this message]
2007-07-01 16:25 ` Ulrich Drepper
2007-07-01 17:09 ` Davide Libenzi
2007-07-02 14:09 ` Ulrich Drepper
2007-07-02 22:37 ` Davide Libenzi
2007-07-03 0:28 ` Ulrich Drepper
2007-07-03 0:37 ` Davide Libenzi
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=Pine.LNX.4.64.0706301529310.2957@alien.or.mcafeemobile.com \
--to=davidel@xmailserver.org \
--cc=akpm@linux-foundation.org \
--cc=drepper@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®