From: "Sumankar Shankar" <sumankar@silverpencil.com>
To: linux-kernel@vger.kernel.org
Cc: marcelo@conectiva.com.br
Subject: [PATCH] isofs, 2.4.20
Date: Sun, 16 Feb 2003 03:40:43 +0530 [thread overview]
Message-ID: <3E4F083B.22610.1AB6DD@localhost> (raw)
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
reply other threads:[~2003-02-15 22:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3E4F083B.22610.1AB6DD@localhost \
--to=sumankar@silverpencil.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox