I'm a bit confused. Why exactly is this unacceptable, and what exactly
do you propose instead? Having an entirely separate mount point that is
sort of parallel to the main one, but with extra metadata exposed? So
instead of /path/to/foo/.gfs2_admin/metafile you'd prefer having a
separate mount point like /proc/fs/gfs/path/to/foo/metafile?
Christoph Hellwig wrote:
b) The .gfs2_admin directory exposes the internal files that GFS uses
to store various bits of file system related information. This means
that we've been able to remove virtually all the ioctl() calls from
GFS2. There is one ioctl() call left which relates to
getting/setting GFS2 specific flags on files. The various GFS2 tools
will be updated in due course to use this new interface.
Without even looking at the code a strong NACK here. This is polluting
the namespace which is not acceptable. Please implement a second
filesystem type gfsmeta to do this kind of admin work. Search for ext2meta
which did something similar. Or use a completely different approach,
I'd need to look at the actual functionality provided to give a better
advice, but currently I'm lacking the time for that.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
