From: Andy Whitcroft <apw@canonical.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
vaurora@redhat.com, neilb@suse.de, viro@zeniv.linux.org.uk,
Andy Whitcroft <apw@canonical.com>
Subject: [PATCH 0/2] overlayfs: module and statfs fixes
Date: Fri, 1 Oct 2010 18:48:00 +0100 [thread overview]
Message-ID: <1285955282-10240-1-git-send-email-apw@canonical.com> (raw)
Just been playing with overlayfs and hit a couple of issues. First I
was not able to build this filesystem as a module. Second statfs support
was missing. Following this email are a couple of patches which I used to
fix these up. I am not 100% sure the statfs approach is quite right, but
its not clear the semantics can ever be correct in the face of an overlay.
With these applied I was able to drop an overlay over the top of a very
out of date Ubuntu chroot and upgrade it to the latest and greatest;
all without incident.
Nice.
-apw
Andy Whitcroft (2):
overlayfs: export security_inode_permission to allow overlayfs to be
modular
overlayfs: add statfs support
fs/overlayfs/overlayfs.c | 20 ++++++++++++++++++++
security/security.c | 1 +
2 files changed, 21 insertions(+), 0 deletions(-)
next reply other threads:[~2010-10-01 17:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-01 17:48 Andy Whitcroft [this message]
2010-10-01 17:48 ` [PATCH 1/2] overlayfs: export security_inode_permission to allow overlayfs to be modular Andy Whitcroft
2010-10-01 17:48 ` [PATCH 2/2] overlayfs: add statfs support Andy Whitcroft
2010-10-04 9:49 ` [PATCH 0/2] overlayfs: module and statfs fixes 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=1285955282-10240-1-git-send-email-apw@canonical.com \
--to=apw@canonical.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=neilb@suse.de \
--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).