Re: PROBLEM: I/O system call never returns if file desc is closed in the

From: Alan Cox (alan@lxorguk.ukuu.org.uk)
Date: Wed Jun 06 2001 - 16:35:31 EST

Next message: Kipp Cannon: "Re: temperature standard - global config option?"
Previous message: Alan Cox: "Re: Break 2.4 VM in five easy steps"
In reply to: thierry.lelegard@canal-plus.fr: "PROBLEM: I/O system call never returns if file desc is closed in the meantime"
Next in thread: Matthias Urlichs: "Re: PROBLEM: I/O system call never returns if file desc is closed in the"
Reply: Matthias Urlichs: "Re: PROBLEM: I/O system call never returns if file desc is closed in the"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

> This report describes a problem in the usage of file descriptors across
> multiple threads. When one thread closes a file descriptor, another
> thread which waits for an I/O on that file descriptor is not notified
> and blocks forever.

THe I/O does not block forever, it blocks until completed. The actual final
closure of the object occurs when the last operation on it exits

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Next message: Kipp Cannon: "Re: temperature standard - global config option?"
Previous message: Alan Cox: "Re: Break 2.4 VM in five easy steps"
In reply to: thierry.lelegard@canal-plus.fr: "PROBLEM: I/O system call never returns if file desc is closed in the meantime"
Next in thread: Matthias Urlichs: "Re: PROBLEM: I/O system call never returns if file desc is closed in the"
Reply: Matthias Urlichs: "Re: PROBLEM: I/O system call never returns if file desc is closed in the"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Thu Jun 07 2001 - 21:00:53 EST