linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bharata B Rao <bharata@linux.vnet.ibm.com>
To: David Newall <davidn@davidnewall.com>
Cc: Ulrich Drepper <drepper@redhat.com>,
	bsn.0007@gmail.com, libc-alpha@sourceware.org,
	Jan Blunck <jblunck@suse.de>, Erez Zadok <ezk@cs.sunysb.edu>,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	viro@zeniv.linux.org.uk, Christoph Hellwig <hch@lst.de>,
	Mingming Cao <cmm@us.ibm.com>, Dave Hansen <haveblue@us.ibm.com>,
	Trond Myklebust <trond.myklebust@fys.uio.no>,
	David Woodhouse <dwmw2@infradead.org>
Subject: Re: [RFC PATCH 1/2] Union Mount: glibc readdir support
Date: Mon, 12 May 2008 09:13:41 +0530	[thread overview]
Message-ID: <20080512034341.GA10541@in.ibm.com> (raw)
In-Reply-To: <482058C4.8010104@davidnewall.com>

On Tue, May 06, 2008 at 10:40:28PM +0930, David Newall wrote:
> Bharata B Rao wrote:
> > Is dis-allowing NFS-exporting of unions an option ?
> 
> Is it that simple?  What about a union further in an NFS export?  What
> about union-mounting after the tree has been NFS-exported?

Ok I am realizing that it is not simple. I am actually reading up NFS
code to understand how it supports crossing of mountpoints. I see that
one can mount a filesystem within a NFS export and NFS server would be
able to cross over to that filesystem and provide those contents to the
client. Acutally Union Mount maintains union stack very similar to the
mount stack, but here we walk the union stack down. So I am checking if
something similar to mountpoint crossing would be able to solve the
problem of fetching all the contents of the NFS-exported union.

Answering my question to Erez that I raised in another thread, I see
that Unionfs doesn't set the export_operations in it's superblock and
hence I believe unions created by Unionfs aren't NFS-exportable as of
know. Erez, correct me if I got it wrong.

Regards,
Bharata.

  reply	other threads:[~2008-05-12  3:43 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-29 13:32 [RFC PATCH 0/2] Union Mount: Directory listing in glibc bsn.0007
2008-04-29 13:33 ` [RFC PATCH 1/2] Union Mount: glibc readdir support bsn.0007
2008-05-01  6:08   ` Ulrich Drepper
2008-05-06  4:21     ` Bharata B Rao
2008-05-06  5:46       ` hooanon05
2008-05-06 13:10       ` David Newall
2008-05-12  3:43         ` Bharata B Rao [this message]
2008-05-12  3:49           ` Erez Zadok
2008-05-09 20:05       ` Erez Zadok
2008-04-29 13:34 ` [RFC PATCH 2/2] Union Mount: glibc seekdir support bsn.0007
2008-04-29 15:21 ` [RFC PATCH 0/2] Union Mount: Directory listing in glibc hooanon05
2008-04-29 16:12   ` Jan Blunck
2008-04-29 15:49 ` Erez Zadok
2008-04-29 16:16   ` Jan Blunck
2008-04-30  6:07   ` NAGABHUSHAN BS
2008-04-30 16:35     ` Erez Zadok
2008-05-01  1:39       ` hooanon05
2008-04-29 16:04 ` Jan Blunck
2008-04-30  6:18   ` NAGABHUSHAN BS

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=20080512034341.GA10541@in.ibm.com \
    --to=bharata@linux.vnet.ibm.com \
    --cc=bsn.0007@gmail.com \
    --cc=cmm@us.ibm.com \
    --cc=davidn@davidnewall.com \
    --cc=drepper@redhat.com \
    --cc=dwmw2@infradead.org \
    --cc=ezk@cs.sunysb.edu \
    --cc=haveblue@us.ibm.com \
    --cc=hch@lst.de \
    --cc=jblunck@suse.de \
    --cc=libc-alpha@sourceware.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trond.myklebust@fys.uio.no \
    --cc=viro@zeniv.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;
as well as URLs for NNTP newsgroup(s).