From owner-freebsd-fs@freebsd.org  Sat Jul 29 08:34:39 2017
Return-Path: <owner-freebsd-fs@freebsd.org>
Delivered-To: freebsd-fs@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 3B4C1DBE0DA
 for <freebsd-fs@mailman.ysv.freebsd.org>; Sat, 29 Jul 2017 08:34:39 +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 22CC363E0F
 for <freebsd-fs@FreeBSD.org>; Sat, 29 Jul 2017 08:34:39 +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 v6T8YcVN009286
 for <freebsd-fs@FreeBSD.org>; Sat, 29 Jul 2017 08:34:39 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-fs@FreeBSD.org
Subject: [Bug 221064] zfs should not be able to shadow mount on root
 directory from userspace
Date: Sat, 29 Jul 2017 08:34:39 +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: CURRENT
X-Bugzilla-Keywords: patch
X-Bugzilla-Severity: Affects Many People
X-Bugzilla-Who: wheelcomplex@gmail.com
X-Bugzilla-Status: Open
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-221064-3630-5bVQQwI8Ht@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-221064-3630@https.bugs.freebsd.org/bugzilla/>
References: <bug-221064-3630@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-fs@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 29 Jul 2017 08:34:39 -0000

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

--- Comment #6 from David NewHamlet <wheelcomplex@gmail.com> ---
(In reply to Poul-Henning Kamp from comment #5)

kenv vfs.root.mountfrom=3D"second rootfs(zfs:newtank/rootfs)" and reboot -r=
 will
trigger kernel to stop all running proccess(include first init) and umount
first rootfs. After that, kernel will try to mount second filesystem as roo=
tfs
and execute init from second rootfs.=20

This might be a better way to handle your case.

This is a useful feature similar to switch_root in Linux world which is very
common in embedded linux.

It was introduced by trasz on Sep 18 2015, 5:35 PM.

https://reviews.freebsd.org/D3693

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