From: Ingo Koehne Subject: Re: unable to umount after chroot to a NFS mounted partition Date: Wed, 8 May 2002 12:28:08 +0200 Sender: linux-fsdevel-owner@vger.kernel.org Message-ID: <20020508102808.GA13800@noo.localnet> References: <20020505170924.GA837@noo.localnet> <15573.35005.147582.796024@charged.uio.no> <20020505203431.GA893@noo.localnet> <20020506061824.GA18214@noo.localnet> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Linux FSdevel Return-path: To: Trond Myklebust Content-Disposition: inline In-Reply-To: <20020506061824.GA18214@noo.localnet> List-Id: linux-fsdevel.vger.kernel.org > > i just found out that the problem only arises when mounting the root > > filesystem of the requested nfs server. it turned out that this was wrong. it does not depend on any setting on the server (except for file contents of the requested files). i found out that the f_count of the executable beeing started via chroot is not 0 after it exits. this is due to non balanced calls to get_file() and fput() in nfs_create_request() and nfs_release_request(). it happens only the first time it is started after the fs has been mounted and the missing release happens if you do the chroot with the same executable a second time. when having excessive printk in the kernel and the kernel slows down considerably the problem does not occur. curionsly it depends on the executable being started and for some executables even on the command line options. i still have no idea how this can have anything to do with chroot and i have no more idea what to look for. ingo