Re: [PATCH 2/8] VFS: per inode statfs (core)

[Miklos Szeredi]

> > Yes, possibility for finding out where subfilesystems are located
> > _will_ be missing for such filesystems as sshfs.
> 
> Why? Can't lookup() notice the change in remote st_dev as you cross the
> filesystem boundary?

a) sftp is path based protocol, there's no separate lookup

b) sftp doesn't transfer st_ino or st_dev, they are both made up on
the client side

> For NFS the plan is to automatically submount such remote
> subfilesystems. That fixes a host of problems including the one that you
> mention w.r.t. statfs, the problem of potential duplicate inode numbers,
> etc.

That is fine.  It's clearly a superior sulution when the info is
available.  With sshfs the server simply doesn't care about mounts,
and so this is basically out of the question.

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