Re: signal_pending() and schedule()

Joel Becker (
Tue, 26 Mar 2002 17:49:32 -0800

On Tue, Mar 26, 2002 at 04:19:55PM -0800, Melkor Ainur wrote:
> This works fine for some applications like netcat,etc
> but fails for netscape. In debugging this, I observe
> that after calling schedule_timeout(), the sigpending
> bit appears to be set immediately and thus
> schedule() doesn't actually put the process to sleep.

This is happening exactly for the reason you would expect it to:
A signal has arrived. Netscape's userspace "threading" is based
entirely on signals. Netscape sends itself SIGALRM almost continuously.
You'll have to expect this from Netscape and work around or with it.



Life's Little Instruction Book #337

"Reread your favorite book."

Joel Becker Senior Member of Technical Staff Oracle Corporation E-mail: Phone: (650) 506-8127 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to More majordomo info at Please read the FAQ at