From owner-freebsd-net@FreeBSD.ORG  Thu May  2 14:53:37 2013
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by hub.freebsd.org (Postfix) with ESMTP id 70461D45
 for <freebsd-net@freebsd.org>; Thu,  2 May 2013 14:53:37 +0000 (UTC)
 (envelope-from eric@vangyzen.net)
Received: from aussmtpmrkpc120.us.dell.com (aussmtpmrkpc120.us.dell.com
 [143.166.82.159])
 by mx1.freebsd.org (Postfix) with ESMTP id 45B331124
 for <freebsd-net@freebsd.org>; Thu,  2 May 2013 14:53:36 +0000 (UTC)
X-Loopcount0: from 64.238.244.148
X-IronPort-AV: E=Sophos;i="4.87,597,1363150800"; d="scan'208";a="29489904"
Message-ID: <51827DAA.2020009@vangyzen.net>
Date: Thu, 2 May 2013 09:52:26 -0500
From: Eric van Gyzen <eric@vangyzen.net>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
 rv:17.0) Gecko/20130413 Thunderbird/17.0.5
MIME-Version: 1.0
To: Richard Sharpe <realrichardsharpe@gmail.com>
Subject: Re: Seeing EINVAL from writev on 8.0 to a non-blocking socket even
 though the data seems to hit the wire
References: <CACyXjPwojx1vBo-7bDmN=Pjc2Qp3mRd3Ek2FUjLR_4DC=aUnWA@mail.gmail.com>
 <5181ECDF.1040905@mu.org>
 <CACyXjPy8ctxs1vG0KPLHtaJxrM_YTs6XfLEbhQUBKTkZAjewzA@mail.gmail.com>
In-Reply-To: <CACyXjPy8ctxs1vG0KPLHtaJxrM_YTs6XfLEbhQUBKTkZAjewzA@mail.gmail.com>
Content-Type: text/plain; charset="Big5"
Content-Transfer-Encoding: 7bit
Cc: freebsd-net@freebsd.org, Alfred Perlstein <bright@mu.org>
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 02 May 2013 14:53:37 -0000

On 05/02/2013 08:48, Richard Sharpe wrote:
> On Wed, May 1, 2013 at 9:34 PM, Alfred Perlstein <bright@mu.org> wrote:
>> On 5/1/13 8:03 PM, Richard Sharpe wrote:
>>> 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?
>>>
>> What does the iovec look like when you get EINVAL? Can you sanity check
>> it? Is there anything special about it? (zero length vecs?)
>>
>> I think there are a few "maxvals" that if overrun cause EINVAL to be
>> returned. example is if your iovec is somehow huge or has many, many
>> elements.
> Can anyone tell me the call graph down to the TCP code?
>

writev kern/sys_generic.c
kern_writev
dofilewrite
fo_write in sys/file.h
soo_write in kern/sys_socket.c
sosend in kern/uipc_socket.c
sosend_generic
tcp_usr_send in netinet/tcp_usrreq.c

Eric