Date: Wed, 1 May 2013 20:03:24 -0700 From: Richard Sharpe <realrichardsharpe@gmail.com> To: freebsd-net@freebsd.org Subject: Seeing EINVAL from writev on 8.0 to a non-blocking socket even though the data seems to hit the wire Message-ID: <CACyXjPwojx1vBo-7bDmN=Pjc2Qp3mRd3Ek2FUjLR_4DC=aUnWA@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
Hi folks, I am checking to see if there are any known bugs with respect to this in FreeBSD 8.0. Situation is that Samba 3.6.6 uses writev to a non-blocking socket to get the SMB2 requests on the wire. Intermittently, we see the writev return EINVAL even though the data has gotten on the wire. This I have verified by grabbing a capture and comparing the SMB Sequence number in the last outgoing packet on the wire vs the in-memory contents when we get EINVAL. Sometimes it occurs on a four-element IOVEC, sometimes we get EAGAIN on the four-element IOVEC and then we get EINVAL when retrying on a smaller IOVEC. Where should I look to check if there is some path where this might be happening? Is this even the correct mailing list? --=20 Regards, Richard Sharpe (=A6=F3=A5H=B8=D1=BC~=A1H=B0=DF=A6=B3=A7=F9=B1d=A1C--=B1=E4=BE=DE)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CACyXjPwojx1vBo-7bDmN=Pjc2Qp3mRd3Ek2FUjLR_4DC=aUnWA>