From: Benjamin Herrenschmidt <bh40@calva.net>
To: "D.J. Barrow" <barrow_dj@yahoo.com>, linuxppc-dev@lists.linuxppc.org
Subject: Re: I believe I found a bug in /arch/ppc/kernel/signal.c
Date: Mon, 22 Feb 1999 19:53:04 +0100 [thread overview]
Message-ID: <19990222195304.000021@mail.mipsys.com> (raw)
In-Reply-To: <19990222143657.28939.rocketmail@send206.yahoomail.com>
On Mon, Feb 22, 1999, D.J. Barrow <barrow_dj@yahoo.com> wrote:
>The bug manifested itself in tftp, when longjmp'ing out
>of the signal handler on timeouts.
>
>Resulting in....
>a )sys_sigreturn not get called
>b) signals queued & trampoline stuff on the user stack being trashed.
>c) SIGALRM being blocked forever.
Note also that the people doing ShapeShifter (Mac runtime) told they are
having problem with alternate signal stacks. I didn't look very in depth
at the code, it looks like it's here but I didn't tested. I don't have
more details about their exact problem but if someone is going to look at
the signal stuffs, then think about eventually testing the alt stack.
(I think they need this because parts of MacOS ROM code will use R1 for
something else than stack, I love Apple ;-)
--
E-Mail: <mailto:bh40@calva.net>
BenH. Web : <http://calvaweb.calvacom.fr/bh40/>
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]
next prev parent reply other threads:[~1999-02-22 18:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-22 14:36 I believe I found a bug in /arch/ppc/kernel/signal.c D.J. Barrow
1999-02-22 18:53 ` Benjamin Herrenschmidt [this message]
1999-02-23 14:35 ` Lauro Whately
-- strict thread matches above, loose matches on Subject: below --
1999-02-24 12:45 D.J. Barrow
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=19990222195304.000021@mail.mipsys.com \
--to=bh40@calva.net \
--cc=barrow_dj@yahoo.com \
--cc=linuxppc-dev@lists.linuxppc.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.