From: Jesper Nilsson <jesper.nilsson@axis.com>
To: Rabin Vincent <rabin@rab.in>
Cc: Jesper Nilsson <jespern@axis.com>,
linux-cris-kernel <linux-cris-kernel@axis.com>,
"viro@zeniv.linux.org.uk" <viro@zeniv.linux.org.uk>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/3] CRISv32: handle multiple signals
Date: Mon, 9 Feb 2015 10:52:33 +0100 [thread overview]
Message-ID: <20150209095232.GK11399@axis.com> (raw)
In-Reply-To: <1423428304-26586-3-git-send-email-rabin@rab.in>
On Sun, Feb 08, 2015 at 09:45:04PM +0100, Rabin Vincent wrote:
> Al Viro noted that CRIS fails to handle multiple signals.
>
> This fixes the problem for CRISv32 by making it use a C work_pending
> handling loop similar to the ARM implementation in 0a267fa6a15d41c
> ("ARM: 7472/1: pull all work_pending logics into C function").
>
> This also happens to fixes the warnings which currently trigger on
> CRISv32 due to do_signal() being called with interrupts disabled.
> Reported-by: Al Viro <viro@ZenIV.linux.org.uk>
> Signed-off-by: Rabin Vincent <rabin@rab.in>
Nice, added in the CRIS tree for 3.20.
/^JN - Jesper Nilsson
--
Jesper Nilsson -- jesper.nilsson@axis.com
next prev parent reply other threads:[~2015-02-09 9:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-08 20:45 [PATCH 1/3] CRISv32: don't attempt syscall restart on irq exit Rabin Vincent
2015-02-08 20:45 ` [PATCH 2/3] CRISv32: prevent bogus restarts on sigreturn Rabin Vincent
2015-02-09 9:51 ` Jesper Nilsson
2015-02-08 20:45 ` [PATCH 3/3] CRISv32: handle multiple signals Rabin Vincent
2015-02-09 2:03 ` Guenter Roeck
2015-02-09 9:57 ` Jesper Nilsson
2015-02-09 14:16 ` Guenter Roeck
2015-02-09 16:57 ` Guenter Roeck
2015-02-10 8:21 ` Jesper Nilsson
[not found] ` <CAJy5ezog4wmV13muOsVopwYhV7QYE6kwqFtJx0rsh+5Z4bf1tg@mail.gmail.com>
2015-02-10 12:26 ` Guenter Roeck
2015-02-09 9:52 ` Jesper Nilsson [this message]
2015-02-09 9:49 ` [PATCH 1/3] CRISv32: don't attempt syscall restart on irq exit Jesper Nilsson
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=20150209095232.GK11399@axis.com \
--to=jesper.nilsson@axis.com \
--cc=jespern@axis.com \
--cc=linux-cris-kernel@axis.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rabin@rab.in \
--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.