From: "D.J. Barrow" <barrow_dj@yahoo.com>
To: Lauro Whately <whately@cos.ufrj.br>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: I believe I found a bug in /arch/ppc/kernel/signal.c
Date: Wed, 24 Feb 1999 04:45:06 -0800 (PST) [thread overview]
Message-ID: <19990224124506.12141.rocketmail@send205.yahoomail.com> (raw)
Thanks Lauro,
setjmp in glibc2 compiles to sigsetjmp(env,0) i.e. it doesn't save the
environment.
The sigsetjmp gets rid of the signal being blocked issue ( the main
symptom ), there still can be outstanding signals on the user stack
being trashed though.
---Lauro Whately <whately@cos.ufrj.br> wrote:
>
> > 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.
>
> Have you tried the sigsetjmp/siglongjmp ?
> I've met a similar problem a month ago and found that POSIX.1 does not
> specify the effect of setjmp and longjmp on signal masks (SVR4 does
not save
> and restore the signal mask under setjmp/longjmp, however 4.3 BSD
save and
> restore the signal mask) Instead, two new functions sigsetjmp and
siglongjmp
> are defined by POSIX.1
> Those new ones are working ok with linux 2.1.x releases (I've been
using them
> with linuxppc 2.1.112)
> It seems that the behavior of sigsetjmp/siglongjmp was changed to
the POSIX.1
> specification around the release 2.1.112.
>
> --
> Lauro Whately
> Parallel Computing Lab. / COPPE
> Federal University of Rio de Janeiro
> Brazil
> =====================================
> "A distributed system is one on which I cannot get any work done,
because a
> machine I have never heard of has crashed." -- Leslie Lamport
>
>
>
>
_________________________________________________________
DO YOU YAHOO!?
Get your free @yahoo.com address at http://mail.yahoo.com
[[ 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 reply other threads:[~1999-02-24 12:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-24 12:45 D.J. Barrow [this message]
-- strict thread matches above, loose matches on Subject: below --
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
1999-02-23 14:35 ` Lauro Whately
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=19990224124506.12141.rocketmail@send205.yahoomail.com \
--to=barrow_dj@yahoo.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=whately@cos.ufrj.br \
/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).