> > It's pretty easy to create.  I had a patch:
> > 
> >   http://marc.theaimsgroup.com/?l=linux-fsdevel&m=110099238515110&w=2
> > 
> > to which Greg had a comment:
> > 
> >   http://marc.theaimsgroup.com/?l=linux-fsdevel&m=110114650113580&w=2
> > 
> > which I fixed, but I can't find it anymore.
> 
> Care to resend your fixed patch?

OK, here it is (untested).  reiser4 in -mm used to create /sys/fs for
itself, but it doesn't seem to do so anymore, so it should be safe.

---
This patch adds an empty /sys/fs, which filesystems can use.

Signed-off-by: Miklos Szeredi <[EMAIL PROTECTED]>

Index: linux/include/linux/fs.h
===================================================================
--- linux.orig/include/linux/fs.h       2005-08-31 12:51:30.000000000 +0200
+++ linux/include/linux/fs.h    2005-08-31 12:58:12.000000000 +0200
@@ -1251,6 +1251,9 @@ extern long do_mount(char *, char *, cha
 
 extern int vfs_statfs(struct super_block *, struct kstatfs *);
 
+/* /sys/fs */
+extern struct subsystem fs_subsys;
+
 #define FLOCK_VERIFY_READ  1
 #define FLOCK_VERIFY_WRITE 2
 
Index: linux/fs/namespace.c
===================================================================
--- linux.orig/fs/namespace.c   2005-08-19 14:58:53.000000000 +0200
+++ linux/fs/namespace.c        2005-08-31 12:55:48.000000000 +0200
@@ -43,6 +43,9 @@ static struct list_head *mount_hashtable
 static int hash_mask, hash_bits;
 static kmem_cache_t *mnt_cache; 
 
+/* /sys/fs */
+decl_subsys(fs, NULL, NULL);
+
 static inline unsigned long hash(struct vfsmount *mnt, struct dentry *dentry)
 {
        unsigned long tmp = ((unsigned long) mnt / L1_CACHE_BYTES);
@@ -1453,6 +1456,7 @@ void __init mnt_init(unsigned long mempa
                i--;
        } while (i);
        sysfs_init();
+       subsystem_register(&fs_subsys);
        init_rootfs();
        init_mount_tree();
 }
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to