Re: [PATCH] Support ISO-9660 RockRidge v. 1.12 V2

From: James Lamanna
Date: Thu Oct 19 2006 - 11:40:13 EST


On 10/19/06, Joerg Schilling <Joerg.Schilling@xxxxxxxxxxxxxxxxxxx> wrote:
James Lamanna <jlamanna@xxxxxxxxx> wrote:

>
> Joerg Schilling pointed out that RockRidge v. 1.12 extends the PX entry.
> This patch stores the inode number that is now included.
> He has also mentioned 'implementing support for new inode features' wrt to a
> mkisofs fingerprint. Perhaps that will come at a later date.
> Regardless, that can be built on this patch since now the inode number gets
> stored.
>
> This patch has been tested against mounting an ISO-9660 image in
> loopback that supports RockRidge v. 1.12 (thank you to Joerg for a beta
> of mkisofs that does this).
> This should apply against the latest git.

Let me add some more notes:

The linux NFS server interface is unnecessarily complex and will make it
a lot harder than a "single line change" to make the filesystem correct in case
Linux likes to benefit from the inode numbers in RRip 1.12 to support correct
hardlinks.

If you believe that you understand the NFS server issues, you should fix the
code so that NFS exports will work correctly after the change. If you don't know
what's going on there, you may need to spend a few days with testing and
debugging.

Note that you need to be able to "re-open" any file from a NFS file handle only...
There are many constraints that need to be redeemed and the new algorithm needs
to work correctly with old and with new media.

Hopefully I will have some time to test this box as a NFS server soon.
Unfortunately, hacking on Linux is not exactly my full-time job at the
moment.
Anyways, the patch should probably be put on hold until these
potential issues are addressed. Everything should still function fine
without any RR 1.12 patch.

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