From: Jamie Lokier <jamie@shareable.org>
To: Andreas Dilger <adilger@sun.com>
Cc: Abhijit Paithankar <apaithan@akamai.com>,
linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
Dave Chinner <david@fromorbit.com>,
Joel Becker <joel.becker@oracle.com>
Subject: Re: [RFC PATCH] Filesystem Journal Notifications
Date: Sat, 20 Sep 2008 16:51:42 +0100 [thread overview]
Message-ID: <20080920155142.GC6061@shareable.org> (raw)
In-Reply-To: <20080919203402.GI10950@webber.adilger.int>
Andreas Dilger wrote:
> That assumes agreement between the applications that are using this
> interface. It isn't at all desirable that applications have to know
> the "mountpoint" of the filesystem in order to use inotify, and in
> some cases (e.g. bind mount in a new namespace) there isn't even access
> to the root inode.
A filesystem's root inode needn't be mounted at all.
You don't need a new namespace - bind mount is enough by itself.
It has me wondering - how can an application even tell when it has the
root inode of a filesystem? You can't tell from /etc/mtab or
/proc/mounts, nor from traversing the filesystem itself - except for
filesystems where you know the expected inode number of the root inode.
-- Jamie
next prev parent reply other threads:[~2008-09-20 15:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-12 22:06 [RFC PATCH] Filesystem Journal Notifications Abhijit Paithankar
2008-09-13 9:19 ` Dave Chinner
2008-09-15 2:31 ` Andreas Dilger
2008-09-15 5:39 ` Andreas Dilger
2008-09-15 19:36 ` Abhijit Paithankar
2008-09-15 23:37 ` Andreas Dilger
2008-09-16 23:05 ` Abhijit Paithankar
2008-09-19 20:34 ` Andreas Dilger
2008-09-20 15:51 ` Jamie Lokier [this message]
2008-09-20 5:15 ` Jan Kara
2008-09-23 22:26 ` Andreas Dilger
2008-09-15 13:23 ` Jamie Lokier
2008-09-17 0:06 ` Abhijit Paithankar
2008-09-17 11:35 ` Jamie Lokier
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=20080920155142.GC6061@shareable.org \
--to=jamie@shareable.org \
--cc=adilger@sun.com \
--cc=apaithan@akamai.com \
--cc=david@fromorbit.com \
--cc=joel.becker@oracle.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.