From: Zan Lynx <zlynx@acm.org>
To: Steve Beaty <beaty@emess.mscd.edu>
Cc: chris@scary.beasts.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: sigaction, fork, malloc, and futex
Date: Thu, 06 May 2004 16:22:40 -0600 [thread overview]
Message-ID: <1083882160.8704.18.camel@localhost.localdomain> (raw)
In-Reply-To: <200405062137.i46LbnjF017523@emess.mscd.edu>
[-- Attachment #1: Type: text/plain, Size: 536 bytes --]
On Thu, 2004-05-06 at 15:37, Steve Beaty wrote:
> > I am not sure it is really a problem though. I don't think you should
> > be allowed to fork inside a signal handler. That seems very wrong.
>
> i can't disagree :-) but fork() is supposed to be reentrant...
In your test program, I just tried using sys_clone to fork the process
directly. It works. The problem really is inside glibc. If glibc is
not POSIX compliant in this instance, I suppose you will have to file a
bug with them.
--
Zan Lynx <zlynx@acm.org>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-05-06 22:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-04 20:15 sigaction, fork, malloc, and futex Steve Beaty
2004-05-04 22:30 ` chris
2004-05-04 22:56 ` Zan Lynx
2004-05-04 23:16 ` Andreas Schwab
2004-05-06 21:37 ` Steve Beaty
2004-05-06 22:22 ` Zan Lynx [this message]
2004-05-06 21:36 ` Steve Beaty
2004-05-04 23:37 ` Richard B. Johnson
2004-05-06 21:41 ` Steve Beaty
2004-05-05 0:38 ` Edgar Toernig
2004-05-06 21:47 ` Steve Beaty
[not found] <1SeIE-Dy-17@gated-at.bofh.it>
[not found] ` <1ShG9-2Yt-11@gated-at.bofh.it>
2004-05-04 23:57 ` Pascal Schmidt
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=1083882160.8704.18.camel@localhost.localdomain \
--to=zlynx@acm.org \
--cc=beaty@emess.mscd.edu \
--cc=chris@scary.beasts.org \
--cc=linux-kernel@vger.kernel.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