From owner-freebsd-bugs@freebsd.org  Mon Aug 15 11:57:06 2016
Return-Path: <owner-freebsd-bugs@freebsd.org>
Delivered-To: freebsd-bugs@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 B24C0BBAE7A
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Mon, 15 Aug 2016 11:57:06 +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 A192317F2
 for <freebsd-bugs@FreeBSD.org>; Mon, 15 Aug 2016 11:57:06 +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 u7FBv5RD093199
 for <freebsd-bugs@FreeBSD.org>; Mon, 15 Aug 2016 11:57:06 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 202978] After upgrade of net/syncthing 0.11.18 -> 0.11.23 in
 jail, the jail causes entire host to crash
Date: Mon, 15 Aug 2016 11:57:06 +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.1-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: voltagex@voltagex.org
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-202978-8-2vF1fjtHiC@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-202978-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-202978-8@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-bugs@freebsd.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Aug 2016 11:57:06 -0000

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

Adam Baxter <voltagex@voltagex.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |voltagex@voltagex.org

--- Comment #5 from Adam Baxter <voltagex@voltagex.org> ---
Cannot reproduce with the kernel from 10.3-RELEASE FreeBSD 10.3-RELEASE #0
r297264: Fri Mar 25 02:10:02 UTC 2016
root@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC  amd64

Have tested using syncthing v0.13.4 (portdowngrade net/syncthing r415988) a=
nd
syncthing v0.11.23 (portdowngrade net/syncthing r395632, also requires
portdowngrade lang/go r395390)

I believe this bug, plus #200846 and #201913 can be closed, although someone
with more experience in the kernel itself might want to check when exactly =
this
was resolved, seeing as it's affected 10.1, 10.3 and 11-CURRENT at various
stages.

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