From: Al Viro <viro@ZenIV.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: David Miller <davem@davemloft.net>, linux-kernel@vger.kernel.org
Subject: [git pull] another embarrassing braino fix in signal.git
Date: Sun, 3 Mar 2013 03:10:56 +0000 [thread overview]
Message-ID: <20130303031056.GK4503@ZenIV.linux.org.uk> (raw)
generic compat_sys_rt_sigprocmask() had a very dumb braino; I'd
spent quite a while staring at the offending commit before finally managing
to spot the idiocy ;-/ Dave, could you verify that it fixes all the problems
you've seen on sparc? FWIW, the symptoms I'd been seeing got fixed by that
and AFAICS your reproducer is also taken care of. The fix is definitely
needed; the only question is if there's something else going on. Linus,
please, pull from
git://git.kernel.org/pub/scm/linux/kernel/git/viro/signal for-linus
Shortlog:
Al Viro (1):
fix compat_sys_rt_sigprocmask()
Diffstat:
kernel/signal.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
next reply other threads:[~2013-03-03 3:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-03 3:10 Al Viro [this message]
2013-03-03 4:22 ` [git pull] another embarrassing braino fix in signal.git David Miller
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=20130303031056.GK4503@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--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