Messages in this thread |  | | From | Dan Kegel <> | Subject | Re: [PATCH] thread wakeup fix for 2.4.0-test7 |
| |
Linus wrote: > My claim is that a user program that does a close() on a file that is in > use is inherently racy. Is that so hard to understand?
Unfortunately, Java programs do this a lot, as it's the only reliable way to break a thread out of a blocking I/O call there.
> Just don't close a file descriptor while it is in use. It's that simple. > > (I'm also claiming that Linux will give the most reasonable possible > semantics for the case where you _do_ close the file desciptor when it > is in use. I still claim that you shouldn't do it.)
I'll forward your note to the folks in JSR-51 (Sun's "new I/O for Java" group), fwiw. - Dan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/
|  |