* De: Peter Wemm <[EMAIL PROTECTED]> [ Data: 2003-01-10 ]
[ Subjecte: Re: Serious issues with kqueue on sockets on CURRENT. ]
> In case anybody wants to play, I seem to recall some changes in uipc_socket.c
> that caused some problems (totally hosed the resolver) a while back:
> ----------------------------
> revision 1.134
> date: 2002/11/01 21:27:59; author: kbyanc; state: Exp; lines: +1 -1
> Track the number of non-data chararacters stored in socket buffers so that
> the data value returned by kevent()'s EVFILT_READ filter on non-TCP
> sockets accurately reflects the amount of data that can be read from the
> sockets by applications.
>
> PR: 30634
> Reviewed by: -net, -arch
> Sponsored by: NTT Multimedia Communications Labs
> MFC after: 2 weeks
> ----------------------------
> revision 1.136
> date: 2002/11/05 18:48:46; author: kbyanc; state: Exp; lines: +1 -1
> Fix filt_soread() to properly flag a kevent when a 0-byte datagram is
> received.
>
> Verified by: dougb, Manfred Antar <[EMAIL PROTECTED]>
> Sponsored by: NTT Multimedia Communications Labs
> ----------------------------
>
> Is this related?
I think so, but I think the latter bandaids the brokenness of the former,
to let non-existant 0-byte things occur. People say this should maybe only
happen once, but I let my code just return in that case, and send a message
to the console. Wasn't pretty, for one connection.
How do we read the 0-byte datagram, after all?
Thanx,
juli.
--
Juli Mallett <[EMAIL PROTECTED]>
AIM: BSDFlata -- IRC: juli on EFnet.
OpenDarwin, Mono, FreeBSD Developer.
ircd-hybrid Developer, EFnet addict.
FreeBSD on MIPS-Anything on FreeBSD.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
