Date: Thu, 02 May 2013 07:21:05 +0000 From: "jabbaarbarelly (via Twitter)" <i-serrofq-arg=serrofq.bet-705ae@postmaster.twitter.com> To: freebsd-net@freebsd.org Subject: jabbaarbarelly sent you an invitation Message-ID: <20130502072111.3446AC15@hub.freebsd.org>
next in thread | raw e-mail | index | archive | help
jabbaarbarelly sent you an invitation Twitter helps you stay connected with what's happening right now and with the people and organizations you care about. Accept invitation https://twitter.com/i/6332863a-e7fd-4844-9401-c5bff963cc81 ------------------------ This message was sent by Twitter on behalf of Twitter users who entered your email address to invite you to Twitter. Unsubscribe: https://twitter.com/i/o?t=1&iid=c52b3013-5d30-4d50-8302-8b3d136674f4&uid=0&c=ZNV%2BN6G7N7ilWCy7kazRVC1CjOBTEr2%2B&nid=9+26 Need help? https://support.twitter.com From owner-freebsd-net@FreeBSD.ORG Thu May 2 13:48:42 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 DBDBCDFA for <freebsd-net@freebsd.org>; Thu, 2 May 2013 13:48:42 +0000 (UTC) (envelope-from realrichardsharpe@gmail.com) Received: from mail-wg0-x234.google.com (mail-wg0-x234.google.com [IPv6:2a00:1450:400c:c00::234]) by mx1.freebsd.org (Postfix) with ESMTP id 7684C1DAD for <freebsd-net@freebsd.org>; Thu, 2 May 2013 13:48:42 +0000 (UTC) Received: by mail-wg0-f52.google.com with SMTP id k13so579527wgh.31 for <freebsd-net@freebsd.org>; Thu, 02 May 2013 06:48:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:content-transfer-encoding; bh=umIcw3C+uJGn0/mLhIApaJ3h6SS6XXfklbRNezFxi0Y=; b=NvJ9sXJBXr4VCcCTM/6hw2UaW3Tc2bfkq/18ImPtvOpSS7T7Q0rYxPbyYpGCUu+mOt 8AVFGh2sG+Qn/KyFqReX7+qLc3VJPl3gfjc1atvQVG12rcsHnVEDT+zLqPLi/Q0/nPQ7 viBncvFjR9i/DERB5dGa8As42Xw0ns+UsFvqUBQFZlHxHTZeKDm4OfXw+tHXPTvJKrhI crnneVx1PJJzwKOGiul6n0geQ5kiW3DM4iEHq66jvW7Xqvl4qk8SNq8sKNWQsOl2FJ4S ycK5uY9Z7Ceovh/i1BLuIrTbIohLY1xbMz7RqFfokBDvtxzsNpimSyixC0EMw8IA9HSZ GTFw== MIME-Version: 1.0 X-Received: by 10.180.90.203 with SMTP id by11mr7897378wib.10.1367502521672; Thu, 02 May 2013 06:48:41 -0700 (PDT) Received: by 10.194.179.194 with HTTP; Thu, 2 May 2013 06:48:41 -0700 (PDT) In-Reply-To: <5181ECDF.1040905@mu.org> References: <CACyXjPwojx1vBo-7bDmN=Pjc2Qp3mRd3Ek2FUjLR_4DC=aUnWA@mail.gmail.com> <5181ECDF.1040905@mu.org> Date: Thu, 2 May 2013 06:48:41 -0700 Message-ID: <CACyXjPy8ctxs1vG0KPLHtaJxrM_YTs6XfLEbhQUBKTkZAjewzA@mail.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 From: Richard Sharpe <realrichardsharpe@gmail.com> To: Alfred Perlstein <bright@mu.org> Content-Type: text/plain; charset=Big5 Content-Transfer-Encoding: quoted-printable Cc: freebsd-net@freebsd.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 13:48:42 -0000 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? --=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?20130502072111.3446AC15>