public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Gruenbacher <agruen@suse.de>
To: Christoph Hellwig <hch@infradead.org>
Cc: Eric Paris <eparis@redhat.com>,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	viro@zeniv.linux.org.uk
Subject: Re: [PATCH 1/5] fsnotify/vfsmount: add fsnotify fields to struct vfsmount
Date: Thu, 10 Dec 2009 17:31:42 +0100	[thread overview]
Message-ID: <200912101731.43050.agruen@suse.de> (raw)
In-Reply-To: <20091204153925.GA17062@infradead.org>

On Friday 04 December 2009 16:39:25 Christoph Hellwig wrote:
> What's the rationale for adding them?

The idea is to provide a mechanism to watch for "all events", but in a 
namespace aware way: for that, a process registers interest in all mount 
points it can reach.  With the previous hack, a global "I want it all" flag, 
per-namespace listeners were not possible.

Root can use bind mounts onto themselves (e.g., mount --bind /foo/bar 
/foo/bar) to watch arbitrary directories with the per-mount-point mechanism.  
Mount as user will open up additional use cases.

It would be nice to be able to register interest in all events below a 
directory which is not a mount point, too.  The problem with that is that the 
number of cached inodes below a given directory could be huge -- and we would 
have to visit them all atomically in order to "mark" them, which is not 
feasible.  The per-mount-point mechanism will eventually give us *almost* the 
same, and so I believe it's good enough.

Thanks,
Andreas

  parent reply	other threads:[~2009-12-10 16:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-03  5:53 [PATCH 1/5] fsnotify/vfsmount: add fsnotify fields to struct vfsmount Eric Paris
2009-12-03  5:53 ` [PATCH 2/5] fsnotify: vfsmount marks generic functions Eric Paris
2009-12-03  5:53 ` [PATCH 3/5] fsnotify: Infrastructure for per-mount watches Eric Paris
2009-12-03  5:53 ` [PATCH 4/5] fanotify: should_send_event needs to handle vfsmounts Eric Paris
2009-12-03  5:53 ` [PATCH 5/5] fanotify: infrastructure to add an remove marks on vfsmounts Eric Paris
2009-12-04 15:39 ` [PATCH 1/5] fsnotify/vfsmount: add fsnotify fields to struct vfsmount Christoph Hellwig
2009-12-04 15:46   ` Eric Paris
2009-12-10 16:31   ` Andreas Gruenbacher [this message]
2009-12-15 11:12     ` Niraj kumar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200912101731.43050.agruen@suse.de \
    --to=agruen@suse.de \
    --cc=eparis@redhat.com \
    --cc=hch@infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox