From: Bodo Stroesser <bstroesser@fujitsu-siemens.com>
To: Paul Mackerras <paulus@samba.org>
Cc: David Woodhouse <dwmw2@infradead.org>,
Jeff Dike <jdike@addtoit.com>, Andrew Morton <akpm@osdl.org>,
blaisorblade_spam@yahoo.it, linux-arch@vger.kernel.org,
jdike@ccure.user-mode-linux.org
Subject: Re: [PATCH 9/11] - UML - fix signal mask on delivery error
Date: Thu, 02 Dec 2004 12:40:46 +0100 [thread overview]
Message-ID: <41AEFF3E.1060605@fujitsu-siemens.com> (raw)
In-Reply-To: <16814.64421.960433.460117@cargo.ozlabs.ibm.com>
Paul Mackerras wrote:
> Bodo Stroesser writes:
>
>
>>If a SIGSEGV is forced since the stackframe/sigcontext for a signal-handler
>>could not be created, this SIGSEGV is queued only. To deliver it, do_signal()
>>must be called again, which normally won't happen (with the exception of
>>sys_sigretrun/sys_rt_sigreturn). Thus, SIGSEGV stays in the queue until the
>
>
> We got this right on ppc/ppc64, I believe. After calling do_signal,
> we loop around again (in the exception exit path in entry.S) and check
> the signal pending and reschedule bits again (in the thread_info
> flags). We only exit to usermode when they are both zero.
>
> Paul.
Aha! Sorry, didn't recognize that loop.
Bodo
prev parent reply other threads:[~2004-12-02 11:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-13 2:01 [PATCH 9/11] - UML - fix signal mask on delivery error Jeff Dike
2004-11-13 0:34 ` Andrew Morton
2004-11-14 22:13 ` Jeff Dike
2004-11-15 8:35 ` David Woodhouse
2004-11-22 15:30 ` David Woodhouse
2004-11-15 11:40 ` Bodo Stroesser
2004-11-15 17:18 ` Jeff Dike
2004-11-16 9:39 ` Bodo Stroesser
2004-11-30 14:59 ` David Woodhouse
2004-12-02 9:55 ` Bodo Stroesser
2004-12-02 11:25 ` Paul Mackerras
2004-12-02 11:40 ` Bodo Stroesser [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=41AEFF3E.1060605@fujitsu-siemens.com \
--to=bstroesser@fujitsu-siemens.com \
--cc=akpm@osdl.org \
--cc=blaisorblade_spam@yahoo.it \
--cc=dwmw2@infradead.org \
--cc=jdike@addtoit.com \
--cc=jdike@ccure.user-mode-linux.org \
--cc=linux-arch@vger.kernel.org \
--cc=paulus@samba.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 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.