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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <453749e8.ANSGHhMt8ZPpaILR%Joerg.Schilling@fokus.fraunhofer.de>
Date:	Thu, 19 Oct 2006 11:48:24 +0200
From:	Joerg.Schilling@...us.fraunhofer.de (Joerg Schilling)
To:	schilling@...us.fraunhofer.de, linux-kernel@...r.kernel.org,
	jlamanna@...il.com, ismail@...dus.org.tr
Subject: Re: [PATCH] Support ISO-9660 RockRidge v. 1.12 V2

James Lamanna <jlamanna@...il.com> 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.

And finally a note to Alan Cox:

Instead of being unwilling to follow the Nettiquette by removing people from the
To: list with your replies and instead of sending useless replies that don't help
people, you should better stay quiet.

Jörg

-- 
 EMail:joerg@...ily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin
       js@...tu-berlin.de                (uni)  
       schilling@...us.fraunhofer.de     (work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/