From: Ralf Baechle <ralf@linux-mips.org>
To: David Daney <ddaney@caviumnetworks.com>
Cc: linux-mips@linux-mips.org, florian@openwrt.org
Subject: Re: [PATCH] MIPS: Use force_sig when handling address errors.
Date: Tue, 5 May 2009 21:32:32 +0100 [thread overview]
Message-ID: <20090505203231.GA25433@linux-mips.org> (raw)
In-Reply-To: <1241552987-662-1-git-send-email-ddaney@caviumnetworks.com>
On Tue, May 05, 2009 at 12:49:47PM -0700, David Daney wrote:
> When init is started it is SIGNAL_UNKILLABLE. If it were to get an
> address error, we would try to send it SIGBUS, but it would be ignored
> and the faulting instruction restarted. This results in an endless
> loop.
>
> We need to use force_sig() instead so it will actually die and give us
> some useful information.
>
> Reported-by: Florian Fainelli <florian@openwrt.org>
>
> Signed-off-by: David Daney <ddaney@caviumnetworks.com>
Thanks! Will apply.
Ralf
prev parent reply other threads:[~2009-05-05 20:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-05 19:49 [PATCH] MIPS: Use force_sig when handling address errors David Daney
2009-05-05 20:32 ` Ralf Baechle [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=20090505203231.GA25433@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=ddaney@caviumnetworks.com \
--cc=florian@openwrt.org \
--cc=linux-mips@linux-mips.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