From nobody@FreeBSD.org  Thu Jan  9 06:26:15 2014
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
	(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by hub.freebsd.org (Postfix) with ESMTPS id B2FC9560
	for <freebsd-gnats-submit@FreeBSD.org>; Thu,  9 Jan 2014 06:26:15 +0000 (UTC)
Received: from oldred.freebsd.org (oldred.freebsd.org [IPv6:2001:1900:2254:206a::50:4])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mx1.freebsd.org (Postfix) with ESMTPS id 9F69310D4
	for <freebsd-gnats-submit@FreeBSD.org>; Thu,  9 Jan 2014 06:26:15 +0000 (UTC)
Received: from oldred.freebsd.org ([127.0.1.6])
	by oldred.freebsd.org (8.14.5/8.14.7) with ESMTP id s096QENQ045612
	for <freebsd-gnats-submit@FreeBSD.org>; Thu, 9 Jan 2014 06:26:14 GMT
	(envelope-from nobody@oldred.freebsd.org)
Received: (from nobody@localhost)
	by oldred.freebsd.org (8.14.5/8.14.5/Submit) id s096QEKX045549;
	Thu, 9 Jan 2014 06:26:14 GMT
	(envelope-from nobody)
Message-Id: <201401090626.s096QEKX045549@oldred.freebsd.org>
Date: Thu, 9 Jan 2014 06:26:14 GMT
From: Jens Kassel <jens.kassel@aptilo.com>
To: freebsd-gnats-submit@FreeBSD.org
Subject: in_cksum_skip: out of data by 41310
X-Send-Pr-Version: www-3.1
X-GNATS-Notify:

>Number:         185596
>Category:       kern
>Synopsis:       [bce] in_cksum_skip: out of data by 41310 in 8.4
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Jan 09 06:30:00 UTC 2014
>Closed-Date:    
>Last-Modified:  Sun Apr 20 03:26:37 UTC 2014
>Originator:     Jens Kassel
>Release:        8.4
>Organization:
Aptilo Networks
>Environment:
FreeBSD orbytebuild-freebsd84.sth.aptilo.com 8.4-RELEASE FreeBSD 8.4-RELEASE8 #0 r251259: Mon Jun  3 01:14:28 UTC 2013     root@bake.isc.freebsd.org:/usr/obj/usr/src/sys/GENERIC  i386
>Description:
Hi,


We sometimes see messages like this in dmesg and /var/log/messages

in_cksum_skip: out of data by 15810
in_cksum_skip: out of data by 15810
in_cksum_skip: out of data by 15810
in_cksum_skip: out of data by 15810
in_cksum_skip: out of data by 41310

I have checked with tcpdump and these messages seems to be triggered
when receiving "ICMP destination unreachable" packets.

Is this a known issue in this release?

Regards,

Jens Kassel
>How-To-Repeat:
"ICMP destination unreachable" packets sometimes trigger this issue but
not always.
>Fix:


>Release-Note:
>Audit-Trail:

From: Gleb Smirnoff <glebius@FreeBSD.org>
To: Jens Kassel <jens.kassel@aptilo.com>
Cc: freebsd-gnats-submit@FreeBSD.org
Subject: Re: kern/185596: in_cksum_skip: out of data by 41310
Date: Thu, 9 Jan 2014 14:16:06 +0400

 My guessing is that this messages comes off when a packet in wrong byte order
 enters in_cksum().
 
 Starting with 10.0, our stack doesn't change byte order of IP packets, so
 if my guessing is right, the bug should vanish.
 
 We do not plan any more releases from stable/8 branch. Thus, I'd like
 to close the PR if you don't mind.
 
 -- 
 Totus tuus, Glebius.

From: Jens Kassel <Jens.Kassel@aptilo.com>
To: Gleb Smirnoff <glebius@FreeBSD.org>
Cc: "freebsd-gnats-submit@FreeBSD.org" <freebsd-gnats-submit@FreeBSD.org>
Subject: RE: kern/185596: in_cksum_skip: out of data by 41310
Date: Tue, 14 Jan 2014 08:01:59 +0000

 Hi,
 
 I have not tested this on FreeBSD 10.
 
 But I found that the problem can only be reproduced when using the bce driver.
 Tested with both re & bge drivers and with these the problem cannot be
 reproduced.
 
 Checked SVN history for bce but could not find any commit that seemed to be
 related to this issue.
 
 Regards,
 
 Jens
 
From: Gleb Smirnoff <glebius@FreeBSD.org>
To: Jens Kassel <Jens.Kassel@aptilo.com>
Cc: "freebsd-gnats-submit@FreeBSD.org" <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

 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.
>Unformatted:
