You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Chuck Murcko <ch...@telebase.com> on 1996/06/18 20:24:04 UTC
Re: WWW Form Bug Report: "SIGALRM handling in mod_proxy" on UnixWare
Thanks for the report. I'll try to get this fix into the 1.1 release.
lampa@fee.vutbr.cz liltingly intones:
>
> Submitter: lampa@fee.vutbr.cz
> Operating system: UnixWare, version:
> Version of Apache Used: 1.1b4
> Extra Modules used:
> URL exhibiting problem:
>
> Symptoms:
> --
> The change of SIGALRM handling in mod_proxy.c
> is probably not correct. Blocking timeout using
> block_alarms() doesn't disable SIGALRM arrival.
> If this signal arrives, it interrupts some
> kernel call and this will end with EINTR.
> Almost no kernel call in mod_proxy checks this
> (I mean directory traversal, stat, unlink, etc.).
>
> Solution:
> 1. really call alarm(0)
> 2. test EINTR everywhere
> 3. use sigaction() and SA_RESTART (not supported
> on all systems, but works at least on SVR4, Linux,
> and BSD)
>
> --
>
> Backtrace:
> --
>
> --
>
chuck
Chuck Murcko N2K Inc. Wayne PA chuck@telebase.com
And now, on a lighter note:
Real programmers don't comment their code. It was hard to write, it
should be hard to understand.