From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: try_to_freeze() called with IRQs disabled on ARM
Date: Fri, 2 Sep 2011 18:22:59 +0100 [thread overview]
Message-ID: <20110902172259.GA6619@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <OF69A57AB0.CF22689A-ONC12578FF.004EDD71-C12578FF.005142FF@de.ibm.com>
On Fri, Sep 02, 2011 at 04:47:35PM +0200, Ulrich Weigand wrote:
> Assume the scenario you initally describe, where a first signal is
> ignored and leads to system call restart. With your latest patch,
> you call into syscall_restart which sets everything up to restart
> the call (with interrupts disabled).
I don't think SIG_IGN signals even set the TIF work flag, so they
never even cause a call into do_signal(). Therefore, as far as
syscalls go, attempting to send a process (eg) a SIGINT which its
handler is set to SIG_IGN results in the process not even being
notified about the attempt - we won't even wake up while the
syscall is sleeping.
> To really fix this case would probably require some way for the
> debugger to save and restore the restore_block saved state. This
> is not quite trivial, since it would expose that state to user space,
> effectively creating a new ABI (and probably requiring sanity checks
> to ensure a valid state is restored). This probably cannot be fixed
> by one architecture for itself, but would need support from common
> kernel code.
Such state would have to be crytographically signed or kept entirely
within the kernel, as it would otherwise mean that you could redirect
the kernel PC to anywhere...
next prev parent reply other threads:[~2011-09-02 17:22 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-23 15:19 try_to_freeze() called with IRQs disabled on ARM Mark Brown
2011-08-23 15:43 ` Russell King - ARM Linux
2011-08-23 22:08 ` Rafael J. Wysocki
2011-08-23 21:51 ` Rafael J. Wysocki
2011-08-23 21:53 ` Tejun Heo
2011-08-23 22:00 ` Russell King - ARM Linux
2011-08-23 22:08 ` Tejun Heo
2011-08-23 22:13 ` Russell King - ARM Linux
2011-08-23 22:17 ` Tejun Heo
2011-08-23 22:35 ` Tejun Heo
2011-08-24 23:15 ` Rafael J. Wysocki
2011-08-25 12:14 ` Russell King - ARM Linux
2011-08-25 12:17 ` Tejun Heo
2011-08-25 12:25 ` Russell King - ARM Linux
2011-08-25 12:35 ` Tejun Heo
2011-08-25 13:04 ` Russell King - ARM Linux
2011-08-25 13:09 ` Tejun Heo
2011-08-25 14:55 ` Russell King - ARM Linux
2011-08-26 14:44 ` Arnd Bergmann
2011-09-01 13:41 ` Ulrich Weigand
2011-09-01 14:00 ` Russell King - ARM Linux
2011-09-02 14:47 ` Ulrich Weigand
2011-09-02 17:22 ` Russell King - ARM Linux [this message]
2011-09-02 17:40 ` Ulrich Weigand
2011-09-02 17:48 ` Russell King - ARM Linux
2011-09-16 10:31 ` Martin Schwidefsky
2011-09-27 17:45 ` Ulrich Weigand
2011-08-30 20:58 ` Mark Brown
2011-08-30 21:10 ` Russell King - ARM Linux
2012-06-26 16:39 ` Mandeep Singh Baines
2012-06-26 17:16 ` Russell King - ARM Linux
2011-08-23 22:13 ` Rafael J. Wysocki
2011-08-25 11:37 ` Mark Brown
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=20110902172259.GA6619@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).