Re: [PATCH] iso9660 inodes beyond 4GB

[Paul Serice]

> Dumb question: why not simply use a 64-bit type in the inode?

I wasn't sure how to proceed in this direction, but I'll give it
another shot.

It seems natural to use the lower 32 bits as the inode number in this
case, but in general, I'm not sure what precautions I need to take
when switching from a unique inode number to a non-unique inode
number.

For example, at fs/isofs/inode.c:131, the comment warns that the
current isofs code supports NFS implicitly because iget() works.
Because I think I will have to use iget5_locked() now instead of
iget(), I think I stand a good chance of breaking whatever NFS support
is currently available.



>>The patch is about 28K and can be downloaded from the following URL:
>>
>>     http://www.serice.net/shunt/linux-2.6.6-isofs.patch
>
> It goes 404.  Please just send the patch directly to the mailing
> list.

Sorry.  I didn't think my post(s) made it to the list.  So, I took the
patch down.

-
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/