From: hooanon05@yahoo.co.jp
To: Valerie Aurora <vaurora@redhat.com>
Cc: Jan Blunck <jblunck@suse.de>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Christoph Hellwig <hch@infradead.org>,
Andy Whitcroft <apw@canonical.com>,
Scott James Remnant <scott@canonical.com>,
Sandu Popa Marius <sandupopamarius@gmail.com>,
Jan Rekorajski <baggins@sith.mimuw.edu.pl>,
Arnd Bergmann <arnd@arndb.de>,
Vladimir Dronnikov <dronnikov@gmail.com>,
Felix Fietkau <nbd@openwrt.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC] Union mounts/writable overlays design
Date: Mon, 12 Oct 2009 14:19:14 +0900 [thread overview]
Message-ID: <7347.1255324754@jrobl> (raw)
In-Reply-To: <20091011014339.GB12667@shell>
Valerie Aurora:
> In writable overlays, every directory will be copied up to the top
> writable overlay, so /u and /u/usr will both have the same st_dev.
> The copy up happens on lookup, so a stat() will trigger this copy up.
> A directory and a regular file in it will have different st_dev's,
> though. Can you foresee any problems with that?
You're right.
I was confused with another implementation of UnionMount, sorry.
I think I had to sleep well.
J. R. Okajima
prev parent reply other threads:[~2009-10-12 5:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-01 14:55 [RFC] Union mounts/writable overlays design Valerie Aurora
2009-10-01 15:47 ` kevin granade
[not found] ` <7004b08e0910010838i6d0a5f5xeed699be686f6906@mail.gmail.com>
2009-10-01 17:15 ` Valerie Aurora
2009-10-01 17:55 ` Jan Blunck
2009-10-01 20:08 ` kevin granade
2009-10-02 19:15 ` Valerie Aurora
2009-10-01 18:49 ` Brad Boyer
2009-10-02 15:30 ` hooanon05
2009-10-11 1:43 ` Valerie Aurora
2009-10-12 5:19 ` hooanon05 [this message]
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=7347.1255324754@jrobl \
--to=hooanon05@yahoo.co.jp \
--cc=apw@canonical.com \
--cc=arnd@arndb.de \
--cc=baggins@sith.mimuw.edu.pl \
--cc=dronnikov@gmail.com \
--cc=hch@infradead.org \
--cc=jblunck@suse.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nbd@openwrt.org \
--cc=sandupopamarius@gmail.com \
--cc=scott@canonical.com \
--cc=vaurora@redhat.com \
--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).