linux-kernel - [PATCH 4/5] fuse: use dentry in statfs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <E1G65Tc-0002iG-00@dorka.pomaz.szeredi.hu>
Date:	Thu, 27 Jul 2006 15:00:32 +0200
From:	Miklos Szeredi <miklos@...redi.hu>
To:	akpm@...l.org
CC:	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org
Subject: [PATCH 4/5] fuse: use dentry in statfs

Some filesystems may want to report different values depending on the
path within the filesystem, i.e. one mount is actually several
filesystems.  This can be the case for a network filesystem exported
by an unprivileged server (e.g. sshfs).

This is now possible, thanks to David Howells "VFS: Permit filesystem
to perform statfs with a known root dentry" patch.

This change is backward compatible, so no need to change interface
version.

Signed-off-by: Miklos Szeredi <miklos@...redi.hu>
---

Index: linux/fs/fuse/inode.c
===================================================================
--- linux.orig/fs/fuse/inode.c	2006-07-27 14:38:04.000000000 +0200
+++ linux/fs/fuse/inode.c	2006-07-27 14:38:12.000000000 +0200
@@ -252,6 +252,7 @@ static int fuse_statfs(struct dentry *de
 	memset(&outarg, 0, sizeof(outarg));
 	req->in.numargs = 0;
 	req->in.h.opcode = FUSE_STATFS;
+	req->in.h.nodeid = get_node_id(dentry->d_inode);
 	req->out.numargs = 1;
 	req->out.args[0].size =
 		fc->minor < 4 ? FUSE_COMPAT_STATFS_SIZE : sizeof(outarg);
-
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/