atom feed26 messages in org.freebsd.freebsd-javaclose() of active socket does not wor...
FromSent OnAttachments
Arne H. JuulDec 11, 2006 6:47 am 
Arne H. JuulDec 11, 2006 7:06 am 
Achilleas MantziosDec 11, 2006 7:25 am 
Achilleas MantziosDec 11, 2006 7:48 am 
Kostik BelousovDec 11, 2006 9:11 am 
Arne H. JuulDec 11, 2006 2:40 pm 
David XuDec 11, 2006 4:15 pm 
Arne H. JuulDec 11, 2006 4:25 pm 
Arne H. JuulDec 11, 2006 4:50 pm 
David XuDec 11, 2006 5:04 pm 
Daniel EischenDec 11, 2006 5:08 pm 
Bruce EvansDec 11, 2006 9:54 pm 
Poul-Henning KampDec 11, 2006 10:43 pm 
Daniel EischenDec 12, 2006 5:21 am 
Kostik BelousovDec 12, 2006 5:59 am 
Daniel EischenDec 12, 2006 6:24 am 
Daniel EischenDec 12, 2006 6:35 am 
Kostik BelousovDec 12, 2006 6:38 am 
Greg LewisDec 12, 2006 11:31 am 
Daniel EischenDec 12, 2006 12:49 pm 
David XuDec 12, 2006 3:29 pm 
Arne H. JuulDec 12, 2006 5:59 pm 
Bruce EvansDec 12, 2006 7:28 pm 
Julian ElischerDec 12, 2006 11:12 pm 
Bruce EvansDec 13, 2006 3:28 am 
David XuDec 13, 2006 4:10 am 
Subject:close() of active socket does not work on FreeBSD 6
From:Daniel Eischen (deis@freebsd.org)
Date:Dec 12, 2006 12:49:42 pm
List:org.freebsd.freebsd-java

On Tue, 12 Dec 2006, Poul-Henning Kamp wrote:

In message <2006@delplex.bde.org>, Bruce Evans writes:

On Mon, 11 Dec 2006, Daniel Eischen wrote:

It's probably a nightmare in the kernel too. close() starts looking like revoke(), and revoke() has large problems and bugs in this area.

There is the distinctive difference that revoke() operates on a name and close() on a filedescriptor, but otherwise I agree.

Well, if threads waiting on IO are interruptable by signals, can't we make a new signal that's only used by the kernel and send it to all threads waiting on IO for that descriptor? When it gets out to actually setup the signal handler, it just resumes like it is returning from an SA_RESTART signal handler (which according to another posting would reissue the IO command and get EBADF).