26 messages in org.freebsd.freebsd-javaclose() of active socket does not wor...| From | Sent On | Attachments |
|---|---|---|
| Arne H. Juul | Dec 11, 2006 6:47 am | |
| Arne H. Juul | Dec 11, 2006 7:06 am | |
| Achilleas Mantzios | Dec 11, 2006 7:25 am | |
| Achilleas Mantzios | Dec 11, 2006 7:48 am | |
| Kostik Belousov | Dec 11, 2006 9:11 am | |
| Arne H. Juul | Dec 11, 2006 2:40 pm | |
| David Xu | Dec 11, 2006 4:15 pm | |
| Arne H. Juul | Dec 11, 2006 4:25 pm | |
| Arne H. Juul | Dec 11, 2006 4:50 pm | |
| David Xu | Dec 11, 2006 5:04 pm | |
| Daniel Eischen | Dec 11, 2006 5:08 pm | |
| Bruce Evans | Dec 11, 2006 9:54 pm | |
| Poul-Henning Kamp | Dec 11, 2006 10:43 pm | |
| Daniel Eischen | Dec 12, 2006 5:21 am | |
| Kostik Belousov | Dec 12, 2006 5:59 am | |
| Daniel Eischen | Dec 12, 2006 6:24 am | |
| Daniel Eischen | Dec 12, 2006 6:35 am | |
| Kostik Belousov | Dec 12, 2006 6:38 am | |
| Greg Lewis | Dec 12, 2006 11:31 am | |
| Daniel Eischen | Dec 12, 2006 12:49 pm | |
| David Xu | Dec 12, 2006 3:29 pm | |
| Arne H. Juul | Dec 12, 2006 5:59 pm | |
| Bruce Evans | Dec 12, 2006 7:28 pm | |
| Julian Elischer | Dec 12, 2006 11:12 pm | |
| Bruce Evans | Dec 13, 2006 3:28 am | |
| David Xu | Dec 13, 2006 4:10 am |
| Subject: | close() of active socket does not work on FreeBSD 6 | |
|---|---|---|
| From: | Kostik Belousov (kost...@gmail.com) | |
| Date: | Dec 12, 2006 6:38:06 am | |
| List: | org.freebsd.freebsd-java | |
On Tue, Dec 12, 2006 at 09:08:30AM -0500, Daniel Eischen wrote:
On Tue, 12 Dec 2006, Kostik Belousov wrote:
On Tue, Dec 12, 2006 at 08:18:32AM -0500, Daniel Eischen wrote:
It's also couldn't be entirely solved by fixing it in the threads library. You could still have a non-threaded application that waits on a read operation, but receives a signal and closes the socket in the signal handler.
This is not the problem. The read (as syscall being executed) is aborted when signal is delivered. Original poster considered situation where read() is active (in particular, f_count of struct file is incremented by fget, that caused the reported behaviour).
Even when SA_RESTART is set?
Yes. Since SA_RESTART causes syscall to be reissued, read() would fail with EBADFD on its own.