Re: Fix for thread+network crashes in 2.0/2.1?

Robert M. Fleischman (
Fri, 27 Feb 1998 12:43:15 -0500 (EST)

>>The fact that you saw problems implies that your threads _are_ closing
>>files that are still in use by another thread, and it is possible that
>>"select()" was only one of the uses. The pre-89-3 kernel protects read(),
>>write() and select() (read/write have been there "forever"), but there are
>>other cases that it might not protect against (FASYNC comes to mind: can
>>you think of what operations your application would be using on the
>>sockets it has open in threads?).

How about "mmap()"??

Our code does a lot of:
read/write the mmap()'d memory

Could that be a factor?

>>This may explain why the test-program posted doesn't have problems (it
>>probably only does selects), but your load may have different patterns.

I am fairly sure we don't do things like close() a descriptor that
some other part of the program is in the middle of using. We'd know
about that WAY before now. (Our other O/S's would get upset!)


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to