From: Miklos Szeredi <miklos@szeredi.hu>
To: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: apw@canonical.com
Subject: [PATCH 7/8 v4] overlayfs: add statfs support
Date: Tue, 26 Oct 2010 12:50:35 +0200 [thread overview]
Message-ID: <20101026105110.223625187@szeredi.hu> (raw)
In-Reply-To: <20101026105028.575362331@szeredi.hu>
[-- Attachment #1: ovl-add-statfs-support.patch --]
[-- Type: text/plain, Size: 1851 bytes --]
From: Andy Whitcroft <apw@canonical.com>
Add support for statfs to the overlayfs filesystem. As the upper layer
is the target of all write operations assume that the space in that
filesystem is the space in the overlayfs. There will be some inaccuracy as
overwriting a file will copy it up and consume space we were not expecting,
but it is better than nothing.
Use the upper layer dentry and mount from the overlayfs root inode,
passing the statfs call to that filesystem.
Signed-off-by: Andy Whitcroft <apw@canonical.com>
Signed-off-by: Miklos Szeredi <mszeredi@suse.cz>
---
fs/overlayfs/overlayfs.c | 20 ++++++++++++++++++++
1 file changed, 20 insertions(+)
Index: linux-2.6/fs/overlayfs/overlayfs.c
===================================================================
--- linux-2.6.orig/fs/overlayfs/overlayfs.c 2010-10-26 11:29:29.000000000 +0200
+++ linux-2.6/fs/overlayfs/overlayfs.c 2010-10-26 11:29:32.000000000 +0200
@@ -1963,10 +1963,30 @@ static bool ovl_is_same_inode(struct den
return vfs_is_same_inode(ovl_dentry_lower(d1), ovl_dentry_lower(d2));
}
+/**
+ * ovl_statfs
+ * @sb: The overlayfs super block
+ * @buf: The struct kstatfs to fill in with stats
+ *
+ * Get the filesystem statistics. As writes always target the upper layer
+ * filesystem pass the statfs to the same filesystem.
+ */
+static int ovl_statfs(struct dentry *dentry, struct kstatfs *buf)
+{
+ struct dentry *root_dentry = dentry->d_sb->s_root;
+ struct path path;
+ ovl_path_upper(root_dentry, &path);
+
+ if (!path.dentry->d_sb->s_op->statfs)
+ return -ENOSYS;
+ return path.dentry->d_sb->s_op->statfs(path.dentry, buf);
+}
+
static const struct super_operations ovl_super_operations = {
.put_super = ovl_put_super,
.remount_fs = ovl_remount_fs,
.is_same_inode = ovl_is_same_inode,
+ .statfs = ovl_statfs,
};
struct ovl_config {
--
next prev parent reply other threads:[~2010-10-26 10:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-26 10:50 [PATCH 0/8 v4] overlay filesystem prototype Miklos Szeredi
2010-10-26 10:50 ` [PATCH 1/8 v4] vfs: implement open "forwarding" Miklos Szeredi
2010-10-26 10:50 ` [PATCH 2/8 v4] vfs: make i_op->permission take a dentry instead of an inode Miklos Szeredi
2010-10-26 10:50 ` [PATCH 3/8 v4] vfs: introduce s_op->is_same_inode() Miklos Szeredi
2010-10-26 10:50 ` [PATCH 4/8 v4] vfs: export do_splice_direct() to modules Miklos Szeredi
2010-10-26 10:50 ` [PATCH 5/8 v4] export security_inode_permission to allow overlayfs to be modular Miklos Szeredi
2010-10-26 10:50 ` [PATCH 6/8 v4] overlay filesystem prototype Miklos Szeredi
2010-10-26 10:50 ` Miklos Szeredi [this message]
2010-10-26 10:50 ` [PATCH 8/8 v4] overlay: overlay filesystem documentation 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=20101026105110.223625187@szeredi.hu \
--to=miklos@szeredi.hu \
--cc=apw@canonical.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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®