From owner-freebsd-bugs@FreeBSD.ORG Mon Oct 16 10:00:40 2006 Return-Path: X-Original-To: freebsd-bugs@hub.freebsd.org Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 53EFE16A492 for ; Mon, 16 Oct 2006 10:00:40 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0DCDF43D49 for ; Mon, 16 Oct 2006 10:00:40 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k9GA0d59022050 for ; Mon, 16 Oct 2006 10:00:39 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k9GA0dBC022049; Mon, 16 Oct 2006 10:00:39 GMT (envelope-from gnats) Date: Mon, 16 Oct 2006 10:00:39 GMT Message-Id: <200610161000.k9GA0dBC022049@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Yar Tikhiy Cc: Subject: Re: kern/98414: [libc] fts_read(3) disregards permissions of mounted volume X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Yar Tikhiy List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Oct 2006 10:00:40 -0000 The following reply was made to PR kern/98414; it has been noted by GNATS. From: Yar Tikhiy To: bug-followup@FreeBSD.org, tyomitch@gmail.com Cc: Subject: Re: kern/98414: [libc] fts_read(3) disregards permissions of mounted volume Date: Mon, 16 Oct 2006 13:59:23 +0400 I think that this problem is closely related to the fact that the permissions on the original mountpoint directory affect the ability of a process to access ".." from the mounted filesystem root. See CAVEATS in mount(8) for details. AFAIK fts(3) uses chdir("..") when traversing a directory tree unless FTS_NOCHDIR was specified to fts_open(3). FTS_NOCHDIR is usually no good because it limits the depth of the tree fts(3) is able to traverse to PATH_MAX. Would you agree now that there is no bug to fix and so this PR can be closed? -- Yar