From owner-freebsd-net@freebsd.org  Fri Oct 20 13:52:13 2017
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 268C5E34E80
 for <freebsd-net@mailman.ysv.freebsd.org>;
 Fri, 20 Oct 2017 13:52:13 +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 1465C76C7C
 for <freebsd-net@FreeBSD.org>; Fri, 20 Oct 2017 13:52:13 +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 v9KDqCv3060401
 for <freebsd-net@FreeBSD.org>; Fri, 20 Oct 2017 13:52:12 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-net@FreeBSD.org
Subject: [Bug 217606] Bridge stops working after some days
Date: Fri, 20 Oct 2017 13:52:13 +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: 11.0-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: mops@punkt.de
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-217606-2472-FKMp97Wncw@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-217606-2472@https.bugs.freebsd.org/bugzilla/>
References: <bug-217606-2472@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
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.23
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: Fri, 20 Oct 2017 13:52:13 -0000

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

--- Comment #25 from punkt.de Hosting Team <mops@punkt.de> ---
Hey guys,

I am trying to reproduce the problem on a not yet productive server.
Un(?)fortunately this system is rock-stable for almost two weeks now.

I just noticed that this test system runs 11.1p1 while the problematic serv=
er
runs 11.0p10 - duh!

So ... I'll attach a diff of if_bridge.c of the two releases. Looks like the
areas changed cover locking, handling of fragments and handling of mbufs for
fragments.

Any qualified comment on what might have caused the problem in 11.0 that
changed in 11.1?

Thanks!
Patrick

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