From owner-freebsd-jail@freebsd.org  Mon Jul 24 17:05:04 2017
Return-Path: <owner-freebsd-jail@freebsd.org>
Delivered-To: freebsd-jail@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 A733DCFEB33
 for <freebsd-jail@mailman.ysv.freebsd.org>;
 Mon, 24 Jul 2017 17:05:04 +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 95D3A6FB07
 for <freebsd-jail@FreeBSD.org>; Mon, 24 Jul 2017 17:05:04 +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 v6OH53jA059358
 for <freebsd-jail@FreeBSD.org>; Mon, 24 Jul 2017 17:05:04 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-jail@FreeBSD.org
Subject: [Bug 213896] when starting vimage jails the kernel crashes
Date: Mon, 24 Jul 2017 17:05:04 +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 Only Me
X-Bugzilla-Who: stefan@gronke.net
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-jail@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-213896-9824-wZEWRl3c7x@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-213896-9824@https.bugs.freebsd.org/bugzilla/>
References: <bug-213896-9824@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-jail@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: "Discussion about FreeBSD jail\(8\)" <freebsd-jail.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-jail>,
 <mailto:freebsd-jail-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-jail/>
List-Post: <mailto:freebsd-jail@freebsd.org>
List-Help: <mailto:freebsd-jail-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-jail>,
 <mailto:freebsd-jail-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Jul 2017 17:05:04 -0000

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

--- Comment #10 from gronke <stefan@gronke.net> ---
I used a similar script to reproduce the bug and noticed it only occurs when
the host's epair nic went up before destroying the jail.

This snippet manually attaches the nic to the jail after it was started and
takes "yes" as first argument to change the host's nic state.

$ ./crash-demo.sh no
...
> done
$ ./crash-demo.sh yes
> crash

--

#!/bin/sh

UPDOWNIF=3D"$1"
BRIDGE_IF=3Dbridge1

ifconfig $BRIDGE_IF create
set -x

for i in $(seq 0 200); do

  #jail -c vnet persist path=3D$RELEASE_FOLDER name=3Djail-vnet
  jail -c vnet persist name=3Djail-vnet

  epair_a=3D"$(ifconfig epair create)"
  epair_b=3D"$(echo $epair_a | rev | cut -c2- | rev)b"

  mac_a=3D$(openssl rand -hex 6 | sed 's/\(..\)/\1:/g; s/.$//')

  ifconfig $epair_a name a-$i
  ifconfig a-$i ether "$mac_a"

  if [ "$UPDOWNIF" =3D=3D "yes" ]; then
    ifconfig a-$i up
  fi

  ifconfig $BRIDGE_IF addm a-$i
  ifconfig $epair_b vnet jail-vnet

  jexec jail-vnet /sbin/ifconfig $epair_b name vnet0
  jexec jail-vnet /sbin/ifconfig vnet0 up
  jexec jail-vnet /sbin/ifconfig

  jail -r jail-vnet

  if [ "$UPDOWNIF" =3D=3D "yes" ]; then
    ifconfig a-$i down
  fi
  ifconfig $BRIDGE_IF deletem a-$i
  ifconfig a-$i destroy

done

echo "done"

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