Messages in this thread | | | Date | Mon, 16 Nov 1998 00:02:20 +0100 (CET) | From | Andrea Arcangeli <> | Subject | Re: 2.1.128 Lock |
| |
On Sun, 15 Nov 1998, Simon Kirby wrote:
>And spawn just one child. I got a whole wad of messages similar to: > >schedule_timeout: wrong timeout value fffffffb from c012b4d0
Even if it seems that select is buggy, the kernel is safe and these messages could be safely ignored. Due the fact the kernel is safe you are seeing the schedule_timeout() error messages ;-).
Probably it would be better to do the check also in select() and in nanosleep() just to avoid malicious log-flooding attacks.
>...those timeout values are suspicious.
I just added a superflous check in select poll and nanosleep after the time->jiffies conversions to avoid userspace to generate printk() and left the schedule_timeout() message to real kernel errors. I' ll sync/forward these not urgent fixes to Linus when the stall bug will be fixed too.
The fixes are in ftp://e-mind.com/pub/linux/kernel-patches/arca-20..
Thanks for the report Simon!
Andrea Arcangeli
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |