From owner-freebsd-bugs@FreeBSD.ORG Tue Jan 14 19:00:01 2014 Return-Path: Delivered-To: freebsd-bugs@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BDC2DA22 for ; Tue, 14 Jan 2014 19:00:01 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id AA0E31439 for ; Tue, 14 Jan 2014 19:00:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id s0EJ01tk065092 for ; Tue, 14 Jan 2014 19:00:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id s0EJ01GN065091; Tue, 14 Jan 2014 19:00:01 GMT (envelope-from gnats) Date: Tue, 14 Jan 2014 19:00:01 GMT Message-Id: <201401141900.s0EJ01GN065091@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Gleb Smirnoff Subject: Re: kern/185596: in_cksum_skip: out of data by 41310 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: Gleb Smirnoff List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Jan 2014 19:00:01 -0000 The following reply was made to PR kern/185596; it has been noted by GNATS. From: Gleb Smirnoff To: Jens Kassel Cc: "freebsd-gnats-submit@FreeBSD.org" Subject: Re: kern/185596: in_cksum_skip: out of data by 41310 Date: Tue, 14 Jan 2014 22:58:29 +0400 Jens, On Tue, Jan 14, 2014 at 08:01:59AM +0000, Jens Kassel wrote: J> I have not tested this on FreeBSD 10. J> J> But I found that the problem can only be reproduced when using the bce driver. J> Tested with both re & bge drivers and with these the problem cannot be reproduces. J> J> Checked SVN history for bce but could not find any commit that seemed to be related to this issue. If memory serves me well, that were panics with bce(4) and wrong byte order, that urged me to make byte order stable throughout the network stack. However, we didn't find any special in the driver itself after all. It might have a bug, but it also might just exposed a bug in the stack. -- Totus tuus, Glebius.