There is this annoying bug in isofs in 2.4.19 and 2.4.20
that makes it impossible to read most udf written discs
that have been closed as iso9660. Its not a problem in
2.2.x but dont know when in 2.4 it came about. Dunno
if its fixed in 2.4.21-prewhatever but I didnt see any activity
about it in lkml, so the patch is here:
--- linux/fs/isofs/inode.c Sun Feb 16 03:06:39 2003
+++ linux/fs/isofs-mankar/inode.c Sun Feb 16 03:08:34 2003
@@ -939,7 +939,7 @@
if (!ninode)
goto abort;
firstext = ninode->u.isofs_i.i_first_extent;
- sect_size = ninode->u.isofs_i.i_section_size;
+ sect_size = ninode->u.isofs_i.i_section_size >> ISOFS_BUFFER_BITS(inode);
nextino = ninode->u.isofs_i.i_next_section_ino;
iput(ninode);
[The patch is for 2.4.19 but Im quite sure it works
with 2.4.20 too. The error is because iso9660 level 3
support for handling files with more than 2 extents is
badly handled.]
-Mankar
-
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/
This archive was generated by hypermail 2b29 : Sat Feb 15 2003 - 22:01:04 EST