Subject: Re: [PATCH 1/5] fsnotify/vfsmount: add fsnotify fields to struct
 vfsmount
From: Eric Paris <eparis@redhat.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
       viro@zeniv.linux.org.uk, agruen@suse.de
In-Reply-To: <20091204153925.GA17062@infradead.org>
References: <20091203055315.21918.83562.stgit@paris.rdu.redhat.com>
	 <20091204153925.GA17062@infradead.org>
Content-Type: text/plain; charset="UTF-8"
Date: Fri, 04 Dec 2009 10:46:14 -0500
Message-Id: <1259941574.2722.12.camel@localhost>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1024
Lines: 25

On Fri, 2009-12-04 at 10:39 -0500, Christoph Hellwig wrote:
> On Thu, Dec 03, 2009 at 12:53:15AM -0500, Eric Paris wrote:
> > From: Andreas Gruenbacher <agruen@suse.de>
> > 
> > This patch adds the list and mask fields needed to support vfsmount marks.
> > These are the same fields fsnotify needs on an inode.  They are not used,
> > just declared and we note where the cleanup hook should be (the function is
> > not yet defined)
> 
> What's the rationale for adding them?

As opposed to 'global' listeners I've discussed before, Andreas ask me
to write per mount listeners.  It's somewhere in between global and per
inode.  With this series One can now register to listen on a struct
vfsmount instead.  I'll update this patch description to better explain
the point.

-Eric


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/