From owner-freebsd-net@FreeBSD.ORG Thu May 2 03:03:25 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 5FFF7665 for ; Thu, 2 May 2013 03:03:25 +0000 (UTC) (envelope-from realrichardsharpe@gmail.com) Received: from mail-we0-x22b.google.com (mail-we0-x22b.google.com [IPv6:2a00:1450:400c:c03::22b]) by mx1.freebsd.org (Postfix) with ESMTP id EDB791109 for ; Thu, 2 May 2013 03:03:24 +0000 (UTC) Received: by mail-we0-f171.google.com with SMTP id u7so106697wey.16 for ; Wed, 01 May 2013 20:03:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=Y2pQC18xtJg2wBxKQYdoXN3dPVbaU/C0PUYpZcZeDm8=; b=HsFxewYouKmICc5z9LrLbd60EKSdnANwmdCweWXJJ6OaPUTA+sHixDiLTqMZNqqUVt 4X8hQp4yOOwhO9rJfB0+3P84t9s72piJODhMmwE7x1JCkJu+iRx23AbW4eGUxPCC2gBr wBwzqkZ7GWC3yMW74LSbFJZN/rnlz+ko3Dau15q22xmQ+rJHu0fPRF9ZUU62+lXyhThs Gs8AEO5wwWn/ZIy8gWJWaDo6GshpqHkjfBxQNY6YTsD27KTqlPWZu74kQ10h+vQRrQI+ zKnKXg/8UoZbmTM2OLJrLT0MKMngYpCdjHeQJuEJc4ZDaeWOjg1l5dJIfZBo5FG23RWJ AZNQ== MIME-Version: 1.0 X-Received: by 10.180.105.195 with SMTP id go3mr32338366wib.2.1367463804133; Wed, 01 May 2013 20:03:24 -0700 (PDT) Received: by 10.194.179.194 with HTTP; Wed, 1 May 2013 20:03:24 -0700 (PDT) Date: Wed, 1 May 2013 20:03:24 -0700 Message-ID: Subject: Seeing EINVAL from writev on 8.0 to a non-blocking socket even though the data seems to hit the wire From: Richard Sharpe To: freebsd-net@freebsd.org Content-Type: text/plain; charset=Big5 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 May 2013 03:03:25 -0000 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)