From owner-freebsd-bugs@FreeBSD.ORG Mon Jul 19 23:30:05 2010 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 721B21065670 for ; Mon, 19 Jul 2010 23:30:05 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 61E0B8FC08 for ; Mon, 19 Jul 2010 23:30:05 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o6JNU5lP032189 for ; Mon, 19 Jul 2010 23:30:05 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o6JNU5EW032182; Mon, 19 Jul 2010 23:30:05 GMT (envelope-from gnats) Date: Mon, 19 Jul 2010 23:30:05 GMT Message-Id: <201007192330.o6JNU5EW032182@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Jilles Tjoelker Cc: Subject: Re: kern/61810: mounts done within a chroot show up wrong and can't be unmounted from outside. X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Jilles Tjoelker List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jul 2010 23:30:05 -0000 The following reply was made to PR kern/61810; it has been noted by GNATS. From: Jilles Tjoelker To: bug-followup@FreeBSD.org, cliftonr@bass.tikitechnologies.com Cc: Subject: Re: kern/61810: mounts done within a chroot show up wrong and can't be unmounted from outside. Date: Tue, 20 Jul 2010 01:27:54 +0200 Somewhere in 5.x, umount was changed to allow such unmounts. If the passed name matches one in the mount list exactly, the unmount is done by fsid and does not depend on existence of any particular pathname. An fsid may also be specified directly. The "matches exactly" part may become somewhat problematic if vn_fullpath(9) were to be used to return pathnames in statfs returns. Also, vn_fullpath(9) is unreliable and the buffers in the statfs structure are pretty small, so the name as passed to nmount(2) would still be visible in various cases. -- Jilles Tjoelker