From: Denys Vlasenko <vda.linux@googlemail.com>
To: Oleg Nesterov <oleg@redhat.com>
Cc: Denys Vlasenko <dvlasenk@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] epoll_[p]wait: fix spurious -EINTR on ptrace attach
Date: Wed, 26 Jun 2013 09:43:16 +0200 [thread overview]
Message-ID: <201306260943.16210.vda.linux@googlemail.com> (raw)
In-Reply-To: <20130625200623.GA15267@redhat.com>
On Tuesday 25 June 2013 22:06, Oleg Nesterov wrote:
> > > In order to define a "sigset_t ksigmask" member,
> >
> > You do not need it. But the reason is not clear until the cleanup.
>
> I take this back, this is not as simple as I thought... and perhaps even
> not right.
>
> However. Probably you can replace has_ksigmask + ksigmask by
> "sigset_t __user *sigmask" pointer?
This is going to be a PITA because we also need to support
the compat syscall, which uses compat_sigset_t*, not sigset_t*
:(
prev parent reply other threads:[~2013-06-26 7:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-25 15:05 [PATCH] epoll_[p]wait: fix spurious -EINTR on ptrace attach Denys Vlasenko
2013-06-25 18:46 ` Oleg Nesterov
2013-06-25 20:06 ` Oleg Nesterov
2013-06-26 7:43 ` Denys Vlasenko [this message]
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=201306260943.16210.vda.linux@googlemail.com \
--to=vda.linux@googlemail.com \
--cc=dvlasenk@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
/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