From owner-freebsd-net@freebsd.org Wed Feb 20 12:14:13 2019 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 07B7114F2608 for ; Wed, 20 Feb 2019 12:14:13 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 54F55753A9 for ; Wed, 20 Feb 2019 12:14:12 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 0B24514F2607; Wed, 20 Feb 2019 12:14:12 +0000 (UTC) Delivered-To: net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id ECF2614F2606 for ; Wed, 20 Feb 2019 12:14:11 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8B08E753A6 for ; Wed, 20 Feb 2019 12:14:11 +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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id AED4ED73C for ; Wed, 20 Feb 2019 12:14:10 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x1KCEA8r072860 for ; Wed, 20 Feb 2019 12:14:10 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x1KCEA8C072849 for net@FreeBSD.org; Wed, 20 Feb 2019 12:14:10 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 235704] [net] [patch] tun(4) can't be destroyed on a VNET jail if it's renamed Date: Wed, 20 Feb 2019 12:14:10 +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: 12.0-RELEASE X-Bugzilla-Keywords: patch, vimage X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: genneko217@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: 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.29 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Feb 2019 12:14:13 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D235704 --- Comment #5 from genneko217@gmail.com --- Thank you for working on this issue. I've briefly tested the patch and confirmed the reported issue was solved with it. I also confirmed that it changed the way unit numbers are assigned to if_tu= n. While if_tun's unit numbers are assigned sequentially across a host and all jails on it before the patch, it's now assigned independently so that vnet jails and the host can have interfaces with the same name. But now I began to wonder how the interfaces with the same name, say tun0, are related to /dev/tun0 on the system. When I did a quick testing with the following commands, the fourth command removed tun0 interface from the host and also deleted /dev/tun0 while tun0 interface on the vnet jail "test" is still there. Then the fifth command caused a kernel panic at destroy_devl in sys/kern/kern_conf.c. # Assume there's no if_tun on the system. jail -c -n test vnet persist ifconfig tun create jexec test ifconfig tun create ifconfig tun0 destroy jexec test ifconfig tun0 destroy --=20 You are receiving this mail because: You are the assignee for the bug.=