Well, I could fix it with little effort.
>2) It is almost certainly wrong to use "loff_t" for an inode number. Maybe
> you could use "u64" instead? I also think that using "long long"
> explicitly is frowned upon.
I guess its using u64 verses using loff_t. I have chosen the later because
its actually an offset. For fat implementations inode number is nothing but
offset of the directory entry on the disk. So I thought it makes more sense
to use loff_t.
> > I have made changes to fat, vfat and msdos file system implementations in
> > the kernel to use larger data types, thus allowing us to create larger
> > partitions. As per the GPL I would like to make the patch available to
> > everyone and also in case somebody has run into the same problem(who cares
> > about fat in the linux world). The patch has been fairly well tested only
> > on our systems(p3, 700MHz with FC). I truly appreciate if you & anybody in
> > the kernel mailing list have any feedback about the changes.
>
>Does this change the on-disk format for FAT at all, or is it merely a
>kernel filesystem code issue? I think only the latter, but best to check.
Doesn't change on disk format, only fixes implementation.
Thanks,
- Vijay
>Cheers, Andreas
>--
>Andreas Dilger
>http://sourceforge.net/projects/ext2resize/
>http://www-mddsp.enel.ucalgary.ca/People/adilger/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/