From owner-freebsd-bugs@freebsd.org Wed Jan 16 00:57:36 2019 Return-Path: Delivered-To: freebsd-bugs@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 ACC5A149CB66 for ; Wed, 16 Jan 2019 00:57:36 +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 45906839ED for ; Wed, 16 Jan 2019 00:57:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 0115F149CB65; Wed, 16 Jan 2019 00:57:36 +0000 (UTC) Delivered-To: bugs@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 D2BFC149CB64 for ; Wed, 16 Jan 2019 00:57:35 +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 581A4839EC for ; Wed, 16 Jan 2019 00:57:35 +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 8FEED269FD for ; Wed, 16 Jan 2019 00:57:34 +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 x0G0vYPj024362 for ; Wed, 16 Jan 2019 00:57:34 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x0G0vYQq024361 for bugs@FreeBSD.org; Wed, 16 Jan 2019 00:57:34 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: bugs@FreeBSD.org Subject: [Bug 234985] kernel panic when destroying epair interface of vnet jail after using ifconfig inside the jail Date: Wed, 16 Jan 2019 00:57:34 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: panic, vimage X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: henno@schooljan.nl X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status keywords bug_severity priority component assigned_to reporter attachments.created Message-ID: 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.29 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Jan 2019 00:57:37 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D234985 Bug ID: 234985 Summary: kernel panic when destroying epair interface of vnet jail after using ifconfig inside the jail Product: Base System Version: CURRENT Hardware: amd64 OS: Any Status: New Keywords: panic, vimage Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: henno@schooljan.nl Created attachment 201173 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D201173&action= =3Dedit vnet_epair_test.sh: Script for reproducing vnet jail epair destroy panic When creating an epair interface pair for a VNET enabled jail, and then usi= ng ifconfig within this jail, the kernel will often panic later when destroying the jail and finally the epair interface again. However this will not happen when ifconfig is not used within the jail or when it is used outside of the jail, and it will not happen every time. But when it happens, it always hap= pens at the moment the ifconfig destroy epair is done. This has been tested and reproduced on 12.0-RELEASE-p2 and 13.0-CURRENT r343065. I have included a script which reproduces this. It is based on an older scr= ipt which tested for a similar issue, and I changed it so that it will test this 999 times, with an optional 'panic' argument for triggering the critical ifconfig command that makes the difference here. With the panic argument it will reliably panic my system on every run, at w= orst after a couple hundred loops or so (perhaps it is some kind of race condition?). Without the panic argument the system never crashes. I have also included the kernel trace I obtained from the 13.0-CURRENT syst= em, and can supply a kernel memory dump if you need it. So what side effect would this innocent ifconfig command have that it affec= ts a later ifconfig destroy command? It also does not matter which interface you query with it, like when you run ifconfig lo0 or something else, as long as= I use ifconfig at least once I can trigger this. --=20 You are receiving this mail because: You are the assignee for the bug.=