From owner-freebsd-net@freebsd.org  Sat Dec 26 19:07:02 2015
Return-Path: <owner-freebsd-net@freebsd.org>
Delivered-To: freebsd-net@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 108CAA5264B
 for <freebsd-net@mailman.ysv.freebsd.org>;
 Sat, 26 Dec 2015 19:07:02 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 010951502
 for <freebsd-net@FreeBSD.org>; Sat, 26 Dec 2015 19:07:02 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id tBQJ7173023363
 for <freebsd-net@FreeBSD.org>; Sat, 26 Dec 2015 19:07:01 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-net@FreeBSD.org
Subject: [Bug 205592] TCP processing in IPSec causes kernel panic
Date: Sat, 26 Dec 2015 19:07:02 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 10.2-RELEASE
X-Bugzilla-Keywords: crash, needs-qa
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: andrew@rinet.ru
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: mfc-stable9? mfc-stable10?
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-205592-2472-fNGrMuy2hC@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-205592-2472@https.bugs.freebsd.org/bugzilla/>
References: <bug-205592-2472@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <https://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: <https://lists.freebsd.org/mailman/listinfo/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 26 Dec 2015 19:07:02 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205592

--- Comment #2 from andrew@rinet.ru ---
Additional experiments shown that such a panic does not actually connected with
particular protocol, but with packet size.

According to my measures, 'ping -s 146' yet works, but 'ping -s 147' causes
kernel panic.
As these figures have no connection with any kernel structures' size (at least
known to me), I'm in doubt that they can clarify anything.

My kernel has been built with WITNESS and INVARIANTS, but there are no
diagnostic messages at all.

-- 
You are receiving this mail because:
You are the assignee for the bug.