[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <E1O4X02-0003UN-IV@pomaz-ex.szeredi.hu>
Date: Wed, 21 Apr 2010 12:17:42 +0200
From: Miklos Szeredi <miklos@...redi.hu>
To: Jamie Lokier <jamie@...reable.org>
CC: miklos@...redi.hu, jblunck@...e.de, vaurora@...hat.com,
dwmw2@...radead.org, viro@...iv.linux.org.uk,
linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
tytso@....edu, linux-ext4@...r.kernel.org
Subject: Re: [PATCH 13/35] fallthru: ext2 fallthru support
On Wed, 21 Apr 2010, Jamie Lokier wrote:
> Sorry, no: That does not work for bind mounts. Both layers can have
> the same st_dev.
Okay.
> Nor does O_NOFOLLOW stop traversal in the middle of
> a path, there is no handy O_NOCROSSMOUNTS, and no st_mode flag or
> d_type to say it's a bind mount. Bind mounts are really a big pain
> for i_nlink+inotify name counting.
I'm confused. You are monitoring a specific file and would like to
know if something is happening to any of it's links, right?
Why do you need to know about bind mounts for that?
Count the number of times you encounter that d_ino and if that matches
i_nlink then every directory is monitored. Simple as that, no?
Thanks,
Miklos
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists