Date: Fri, 10 Jan 2003 11:25:46 -0200 From: "Daniel C. Sobral" <dcs@tcoip.com.br> To: "Daniel C. Sobral" <dcs@tcoip.com.br> Cc: Tim Robbins <tjr@FreeBSD.ORG>, Juli Mallett <jmallett@FreeBSD.ORG>, current@FreeBSD.ORG, re@FreeBSD.ORG Subject: Re: Serious issues with kqueue on sockets on CURRENT. Message-ID: <3E1EC9DA.50008@tcoip.com.br> In-Reply-To: <20030110013015.A23399@FreeBSD.org> References: <20030110013015.A23399@FreeBSD.org> <20030110215736.A31727@dilbert.robbins.dropbear.id.au> <3E1EB139.6080701@tcoip.com.br>
next in thread | previous in thread | raw e-mail | index | archive | help
Daniel C. Sobral wrote: > Tim Robbins wrote: > > > On Fri, Jan 10, 2003 at 01:30:16AM -0800, Juli Mallett wrote: > > > > > > >Lately, the data field for sockets, which holds bytes ready (in the > > EVFILT_ > > >READ case) to be read, is computed to be zero. This means that if > > you have > > >a low watermark which is >0 per the kq, THE EVENT WILL NEVER HAPPEN. > > Not to > > >mention that this means when the event IS triggered properly (if > you can > > >call it that), it is always said to have =ZERO= bytes ready. > > > > [...] > > > > I can definitely reproduce this here and also fairly angry about it. > > In addition to what you mentioned, fstat() gives an incorrect st_size > > result now and it's likely that non-NOTE_LOWAT low watermarks are > > firing too early as well. > > > > Ugly test program @ http://people.freebsd.org/~tjr/kq.c > > > If I ensure the write only happens after the child is waiting on kq, the > bug does not show up for me. ...because the close() wakes kevent. Indeed, this is completely reproducable here (RELENG_5_0). -- Daniel C. Sobral (8-DCS) Gerencia de Operacoes Divisao de Comunicacao de Dados Coordenacao de Seguranca TCO Fones: 55-61-313-7654/Cel: 55-61-9618-0904 E-mail: Daniel.Capo@tco.net.br Daniel.Sobral@tcoip.com.br dcs@tcoip.com.br Outros: dcs@newsguy.com dcs@freebsd.org capo@notorious.bsdconspiracy.net Q: How was Thomas J. Watson buried? A: 9 edge down. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3E1EC9DA.50008>