From: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
To: Michael Cree <mcree@orcon.net.nz>
Cc: Al Viro <viro@ZenIV.linux.org.uk>,
Al Viro <viro@ftp.linux.org.uk>,
linux-kernel@vger.kernel.org, mattst88@gmail.com,
torvalds@linux-foundation.org, linux-alpha@vger.kernel.org
Subject: Re: [PATCH 1/2] alpha: switch osf_sigprocmask() to use of sigprocmask()
Date: Thu, 30 Sep 2010 15:56:45 +0400 [thread overview]
Message-ID: <20100930115645.GA6037@jurassic.park.msu.ru> (raw)
In-Reply-To: <4CA43E95.5040301@orcon.net.nz>
On Thu, Sep 30, 2010 at 08:39:01PM +1300, Michael Cree wrote:
> It appears to be worse than that. It introduces a regression. On boot up
> on a Compaq Alpha XP1000 the system appears to freeze at the point of
> mounting swap. It eventually resumes after almost three minutes and
> continues to boot. A bisection returned this very commit as the first bad
> commit. With a kernel without this commit the (truncated) bootup log is:
Confirmed, I see some processes get stuck, apparently waiting for signals.
Looks like yet another typo - _BLOCKABLE is defined as
(~(sigmask(SIGKILL) | sigmask(SIGSTOP))), so (newmask & ~_BLOCKABLE)
clears everything but SIGKILL and SIGSTOP.
Ivan.
diff --git a/arch/alpha/kernel/signal.c b/arch/alpha/kernel/signal.c
index d290845..6f7feb5 100644
--- a/arch/alpha/kernel/signal.c
+++ b/arch/alpha/kernel/signal.c
@@ -48,7 +48,7 @@ SYSCALL_DEFINE2(osf_sigprocmask, int, how, unsigned long, newmask)
sigset_t mask;
unsigned long res;
- siginitset(&mask, newmask & ~_BLOCKABLE);
+ siginitset(&mask, newmask & _BLOCKABLE);
res = sigprocmask(how, &mask, &oldmask);
if (!res) {
force_successful_syscall_return();
prev parent reply other threads:[~2010-09-30 11:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-26 18:28 Al Viro
2010-09-28 9:39 ` Michael Cree
2010-09-29 1:07 ` Al Viro
2010-09-30 7:39 ` Michael Cree
2010-09-30 11:50 ` Al Viro
2010-09-30 11:56 ` Ivan Kokshaysky [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=20100930115645.GA6037@jurassic.park.msu.ru \
--to=ink@jurassic.park.msu.ru \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mattst88@gmail.com \
--cc=mcree@orcon.net.nz \
--cc=torvalds@linux-foundation.org \
--cc=viro@ZenIV.linux.org.uk \
--cc=viro@ftp.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 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®