[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1176922847.6796.127.camel@heimdal.trondhjem.org>
Date: Wed, 18 Apr 2007 15:00:47 -0400
From: Trond Myklebust <trond.myklebust@....uio.no>
To: Christoph Hellwig <hch@...radead.org>
Cc: Miklos Szeredi <miklos@...redi.hu>, ebiederm@...ssion.com,
serue@...ibm.com, linuxram@...ibm.com,
linux-fsdevel@...r.kernel.org, viro@....linux.org.uk,
containers@...ts.osdl.org, akpm@...ux-foundation.org,
linux-kernel@...r.kernel.org
Subject: Re: [Devel] Re: [patch 05/10] add "permit user mounts in new
namespace" clone flag
On Wed, 2007-04-18 at 16:01 +0100, Christoph Hellwig wrote:
> I suspect the right answer here is to make nfs mount handling smarter.
> The way mounting works the filesystem is allowed to choose whether it
> can re-used a superblock or needs a new one. In the NFS case we probably
> want to allow multiple superblocks for the same export if important
> paramaters like the security model mismatch.
It might also be another application for layering. If I were able to
share enough of the inode and dentry information between superblocks,
then all sorts of interesting possibilities arise...
Cheers
Trond
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists