Re: Subject: [PATCH 01/16] Squashfs: inode operations
From: David P. Quigley
Date: Tue Oct 21 2008 - 12:35:29 EST
On Fri, 2008-10-17 at 18:53 +0200, JÃrn Engel wrote:
> None of the comments below are a reason against mainline inclusion, imo.
> They should get handled, but whether that happens before or after a
> merge doesn't really matter.
> On Fri, 17 October 2008 16:42:50 +0100, Phillip Lougher wrote:
> > +#include <linux/squashfs_fs.h>
> > +#include <linux/squashfs_fs_sb.h>
> > +#include <linux/squashfs_fs_i.h>
> Current verdict seems to be that these files should live in fs/squashfs/,
> not include/linux/. No kernel code beside squashfs needs the headers
> and userspace tools should have a private copy.
I looked at where filesystems such as ext3 store these and it seems to
be in include/linux. I'm assuming this is because usespace utilities
like fsck need them. It seems wrong for userspace tools to have their
own private copy since you can potentially have them out of sync with
the kernel you are running and it provides more chance for you
forgetting to update a structure somewhere.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/