Has anyone seen writev on FreeBSD return EINVAL after a write to a socket even though the data has hit the wire?

Jeremy Allison jra at samba.org
Thu May 2 10:11:54 MDT 2013


On Wed, May 01, 2013 at 08:52:52PM -0700, Richard Sharpe wrote:
> Hi folks,
> 
> I am seeing a problem with SMB2 and writev's of responses, usually
> large responses, like a 64kiB read response. writev is returning
> EINVAL even though the data has actually hit the wire. I have verified
> this by looking at the capture and comparing the SMB sequence number
> in the header of the packet on the wire with what is in memory pointed
> to by the iovec sent to writev.
> 
> It is most strange, and I am unable to think how this might happen.

At this point you need kernel tracing to find the bug
in FreeBSD. You might want to ping Julian about this.

Jeremy.


More information about the samba-technical mailing list