From: Paolo Giarrusso <p.giarrusso@gmail.com>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Andrew Morton <akpm@linux-foundation.org>,
Jeff Dike <jdike@addtoit.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [uml-devel] [PATCH] UML - Fix irqstack crash
Date: Thu, 20 Sep 2007 17:57:49 +0200 [thread overview]
Message-ID: <200709201757.56298.p.giarrusso@gmail.com> (raw)
In-Reply-To: <20070918170733.c6399124.akpm@linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 1070 bytes --]
On mercoledì 19 settembre 2007, Andrew Morton wrote:
> On Tue, 18 Sep 2007 19:33:36 -0400
> Jeff Dike <jdike@addtoit.com> wrote:
> > ===================================================================
> > --- linux-2.6.17.orig/arch/um/os-Linux/signal.c 2007-09-09
> > 11:15:37.000000000 -0400 +++
> > linux-2.6.17/arch/um/os-Linux/signal.c 2007-09-18 12:32:40.000000000
> > -0400 @@ -119,7 +119,7 @@ void (*handlers[_NSIG])(int sig, struct
> >
> > void handle_signal(int sig, struct sigcontext *sc)
> > {
> > - unsigned long pending = 0;
> > + unsigned long pending = 1 << sig;
> You want 1UL there.
Yes, indeed - or sign extension on 64bit machines would set to 1 the whole
high-word.
But using long for that mask makes no difference; either int or long long (or
better, either u32 or u64) should be used, given that the used signal range
is the same on 32 and 64bit machines, it should be u32 for normal signals or
u64 if RT-signals are also allowed.
--
"Doh!" (cit.), I've made another mistake!
Paolo Giarrusso, aka Blaisorblade
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-09-20 16:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-18 23:33 [PATCH] UML - Fix irqstack crash Jeff Dike
2007-09-19 0:07 ` Andrew Morton
2007-09-20 15:57 ` Paolo Giarrusso [this message]
2007-09-24 20:01 ` [uml-devel] " Jeff Dike
2007-09-26 15:42 ` Paolo Giarrusso
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=200709201757.56298.p.giarrusso@gmail.com \
--to=p.giarrusso@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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