From: Oleg Nesterov <oleg@redhat.com>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Denys Vlasenko <dvlasenk@redhat.com>,
Eric Wong <normalperson@yhbt.net>,
Jason Baron <jbaron@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] signals: eventpoll: set ->saved_sigmask at the start
Date: Tue, 25 Jun 2013 22:44:47 +0200 [thread overview]
Message-ID: <20130625204447.GA17001@redhat.com> (raw)
In-Reply-To: <20130625203245.GA16451@redhat.com>
On 06/25, Oleg Nesterov wrote:
>
> On 06/25, Al Viro wrote:
> >
> > On Tue, Jun 25, 2013 at 09:57:59PM +0200, Oleg Nesterov wrote:
> > > + if (error == -EINTR)
> > > set_restore_sigmask();
> > > - } else
> > > - set_current_blocked(&sigsaved);
> > > + else
> > > + __set_current_blocked(¤t->saved_sigmask);
> >
> > I don't like that. If anything, we have
> > static inline void restore_saved_sigmask(void)
> > {
> > if (test_and_clear_restore_sigmask())
> > __set_current_blocked(¤t->saved_sigmask);
> > }
> > which means that the last part can be turned into
> > set_restore_sigmask();
> > if (error != -EINTR)
> > restore_saved_sigmask();
>
> set_restore_sigmask() does WARN_ON(!TIF_SIGPENDING).
But if we remove this WARN_ON() we can probably change
set_restore_sigmask() to set TS_RESTORE_SIGMASK and
do saved_mask = blocked.
Perhaps it can even acccept "sigset_t *newmask" and do
set_current_blocked().
Then we can move it up and change the code above to simply as you
suggested. But imho this needs a separate change.
Oleg.
next prev parent reply other threads:[~2013-06-25 20:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-25 19:57 [PATCH 0/2] signals: eventpoll: save/restore_sigmask cleanups Oleg Nesterov
2013-06-25 19:57 ` [PATCH 1/2] signals: eventpoll: do not use sigprocmask() Oleg Nesterov
2013-06-25 19:57 ` [PATCH 2/2] signals: eventpoll: set ->saved_sigmask at the start Oleg Nesterov
2013-06-25 20:23 ` Al Viro
2013-06-25 20:32 ` Oleg Nesterov
2013-06-25 20:44 ` Oleg Nesterov [this message]
2013-06-26 16:48 ` Oleg Nesterov
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=20130625204447.GA17001@redhat.com \
--to=oleg@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dvlasenk@redhat.com \
--cc=jbaron@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=normalperson@yhbt.net \
--cc=viro@ZenIV.linux.org.uk \
/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 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.