From mboxrd@z Thu Jan 1 00:00:00 1970 From: Al Viro Subject: Re: Question about inotify and bind mount. Date: Thu, 10 Jun 2010 22:18:24 +0100 Message-ID: <20100610211824.GD31073@ZenIV.linux.org.uk> References: <20100606042627.GB27289@cynthia.pants.nu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Brad Boyer , linux-fsdevel@vger.kernel.org To: Stef Bon Return-path: Received: from zeniv.linux.org.uk ([195.92.253.2]:44411 "EHLO ZenIV.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752925Ab0FJVS1 (ORCPT ); Thu, 10 Jun 2010 17:18:27 -0400 Content-Disposition: inline In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Sun, Jun 06, 2010 at 12:55:35PM +0200, Stef Bon wrote: > So to get bask to the mount --bind issue. Because the inodes are just > mirrored a inotify request is just handled the same? They are not mirrored. They (and dentries and superblock) are literally the same. mount --bind results in a new vfsmount that does (as any vfsmount) refer to a subtree of some fs. In this case - preexisting subtree. Mount tree consists of vfsmounts; there's nothing that would prohibit several vfsmounts refering to the subtrees of the same dentry tree/same (sub)tree/etc. Al, carefully not saying what he really thinks of inotify; completely unfit for repeating in public...