mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: bulb@ucw.cz, viro@ftp.linux.org.uk, akpm@osdl.org,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 2/8] VFS: per inode statfs (core)
Date: Thu, 27 Oct 2005 08:35:23 -0400	[thread overview]
Message-ID: <1130416523.14036.6.camel@lade.trondhjem.org> (raw)
In-Reply-To: <E1EV338-0001vx-00@dorka.pomaz.szeredi.hu>

to den 27.10.2005 klokka 10:23 (+0200) skreiv 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?

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.

Cheers,
  Trond


  reply	other threads:[~2005-10-27 12:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-24 16:55 Miklos Szeredi
2005-10-25  4:25 ` Al Viro
2005-10-25  5:44   ` Miklos Szeredi
2005-10-26 17:31     ` Jan Hudec
2005-10-26 19:17       ` Miklos Szeredi
2005-10-26 19:52         ` Jan Hudec
2005-10-26 20:10           ` Miklos Szeredi
2005-10-26 20:15             ` Anton Altaparmakov
2005-10-27  8:07             ` Jan Hudec
2005-10-27  8:23               ` Miklos Szeredi
2005-10-27 12:35                 ` Trond Myklebust [this message]
2005-10-27 12:53                   ` Miklos Szeredi

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=1130416523.14036.6.camel@lade.trondhjem.org \
    --to=trond.myklebust@fys.uio.no \
    --cc=akpm@osdl.org \
    --cc=bulb@ucw.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=viro@ftp.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

all inboxes | Powered by JetHome®