From owner-freebsd-net@freebsd.org Tue Mar 14 19:38:16 2017 Return-Path: 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 1BE79D0CB42 for ; Tue, 14 Mar 2017 19:38:16 +0000 (UTC) (envelope-from akoshibe@gmail.com) Received: from mail-qk0-x233.google.com (mail-qk0-x233.google.com [IPv6:2607:f8b0:400d:c09::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CD4231E3 for ; Tue, 14 Mar 2017 19:38:15 +0000 (UTC) (envelope-from akoshibe@gmail.com) Received: by mail-qk0-x233.google.com with SMTP id v127so319050qkb.2 for ; Tue, 14 Mar 2017 12:38:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=M9L+76c1OCJEWtCBwvFYeYmZg/J2AG32IHAe5Gq100w=; b=vLX0mqdx69yLoNWsTbelEqZu/ajcWJNSYpWrmXJesv9M1vfs2SQx17aNgapJXhp+pk qizP7h+AuRfXM4/DAAiXNmsP7erhk+1Np9kgCZ9RKYUi5AMTTGNrLGNTJw4qBaKcczOp 7Jv4XzxkAvW0WeOlnx/NPEA3QZ2T0DXx760kruwkqscjlu2JUbvjGp1vCctak+pTDp/x 1bGYPRyxvq/IaNIESzZT05AC9BW+jRj79N9bSJomCkZU8wJRo00VI6Ep88TQ9ONPS12p wr2YlQDY3me9p26pfWptc2pj6kQGBmzlXCrwet8rA3w1CsEncBPujqehNlmlwnZXR2EC WNmg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=M9L+76c1OCJEWtCBwvFYeYmZg/J2AG32IHAe5Gq100w=; b=LXvwkUasHSSLOOVVobuKlrLk6yljhaCSvov8UxZJJI0qLliODAiA/cpl4JaxBdO787 RB7bvha7LuzxpKF2F2dTwNNOzBfnUq0ZEMM2EGyX8mLAiU6J/M5vAnuNGsC1UJg3zlXj D1ljaHJ4MxQHySWsjktrGR7h9Knj7HooN0Ry+E/kH51ZYj3L1Of/rqZJokzGm6xkylzL oMnR3hL7+Jq3jkgjI+4Iu5zHjz5/4wziVaoYjgqrJlX42+azr58xF2DuRYTTtU0uio7A 4CczUcCwDK51cZ+5kfixfKEp4+m07Idrqk06V1eTAQ5rW1mULr8hi3jgVtc5zR1UZ8O5 AbNw== X-Gm-Message-State: AMke39l7yKcuxzX+u8mXBbM8x+cP25eZTnlLQ2S2LkDJa1Rk36zTd0k9K5jjVtLVW6O+kwHetLl+s3Le49LNQg== X-Received: by 10.55.189.130 with SMTP id n124mr39360358qkf.235.1489520294943; Tue, 14 Mar 2017 12:38:14 -0700 (PDT) MIME-Version: 1.0 Received: by 10.140.17.14 with HTTP; Tue, 14 Mar 2017 12:38:14 -0700 (PDT) In-Reply-To: References: From: Ayaka Koshibe Date: Tue, 14 Mar 2017 12:38:14 -0700 Message-ID: Subject: Re: VNET kernel panic on remove renamed interfaces To: Reshad Patuck Cc: freebsd-net@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Mar 2017 19:38:16 -0000 Hi, This looks identical to the panic that I was seeing. It was just patched in -CURRENT yesterday (r315192) - maybe it's this? https://svnweb.freebsd.org/base?view=revision&revision=315192 Ayaka On Tue, Mar 14, 2017 at 11:25 AM, Reshad Patuck wrote: > Hi, > > I am trying to use vnet and pf to host multiple (100s of) jails on a server with a jailed pf router, which will be spun up and down by a script. > > I rename the epair interfaces so that I know which jail links to which interface (for convenience). > > After I delete the jail and renamed epair the kernel panics when I attempt to recreate the epair. > > I believe this is an issue occurs only when I have renamed the epair. > > This issue seems to be fixed in 12-CURRENT as I can not make it crash on current. However this continues to happen on 11-STABLE and 11.0-RELEASE. > > I have found these which seem to fix something similar issues: > https://svnweb.freebsd.org/base?view=revision&sortby=rev&revision=292604 > https://svnweb.freebsd.org/base/projects/vnet/_scripts/jail-vnet-epair-regression01.sh?view=markup > > I have attached scripts that crash the system for the latest versions on 11.0-RELEASE and 11-STABLE branches. > > Can someone help me find where this problem was fixed? (for 12) and if there are any plans to backport the fix to the 11 branch. > > Also any tips on running 100s of VNET jails on a single box would be much appreciated, and if there is anything I can help test I have some physical and VMware boxes I can test on. > > Kernel version I have tested on: > FreeBSD FreeBSD-11-RELEASE 11.0-RELEASE-p8 FreeBSD 11.0-RELEASE-p8 #1 r315007: Fri Mar 10 17:27:30 UTC 2017 root@FreeBSD-11-RELEASE:/usr/obj/usr/src/sys/VNET amd64 > FreeBSD FreeBSD-11-STABLE 11.0-STABLE FreeBSD 11.0-STABLE #1 r315241: Tue Mar 14 12:58:54 UTC 2017 root@FreeBSD-11-STABLE:/usr/obj/usr/src/sys/VNET amd64 > FreeBSD FreeBSD-12 12.0-CURRENT FreeBSD 12.0-CURRENT #1 r315237: Tue Mar 14 10:17:06 UTC 2017 root@FreeBSD-12:/usr/obj/usr/src/sys/VNET amd64 > > Attached: > vnet-rename-epair.sh - Create and destroy a VNET jail in a loop while renaming the epair interface. This crashes on 11. > vnet-no-rename-epair.sh - Create and destroy a VNET jail while not renaming the epair interface. This does not crash. > info.0 - info file from core dump on FreeBSD-11-STABLE > core.txt.0 - core.txt.0 file from core dump on FreeBSD-11-STABLE > > Best regards, > > Reshad > _______________________________________________ > freebsd-net@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"