From: Jesper Juhl <jju@dif.dk>
To: Barubary <barubary@cox.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ISO9660 bug and loopback driver bug
Date: 26 Feb 2002 12:54:01 +0100 [thread overview]
Message-ID: <1014724445.5666.2.camel@jju_lnx> (raw)
In-Reply-To: <006001c1beb9$ea412690$a7eb0544@CX535256D>
In-Reply-To: <006001c1beb9$ea412690$a7eb0544@CX535256D>
On Tue, 2002-02-26 at 12:37, Barubary wrote:
> First, the ISO9660 bug. The ISO file system driver in Linux doesn't handle
> leap years correctly. It assumes all years divisible by 4 are leap years,
> which is incorrect. For those that don't know the right algorithm, all
> years that (are divisible by 4) and ((not divisible by 100), or (divisible
> by 400)) are leap years. ISO file dates on or after March 1, 2100 will be 1
> day off when viewed under Linux as a result. The bug is in fs/isofs/util.c,
> function iso_date(). This is a very low priority bug, because a) nobody
> cares about ISO file date accuracy including me; and b) it shouldn't matter
> until 2100. Anyone bored enough to fix this? :) I guess I could do it...
>
I'll fix it. I'm still learning about the kernel, and fixing small bugs
is a good way to learn - and this one is on a scale I can handle. :-)
I'll look at it tonight and mail a patch to lkml as soon as the work is
done.
> Now the loopback bug. Files whose size is greater than 2^31-1 don't work
> with the loopback driver. It fails with strange errors, like "device not
> found". This bug prevents DVD-ROM .iso files from being mounted as either
> UDF or ISO file systems - the particular use I encountered it with. It's a
> bit higher of a priority than the ISO9660 date bug, because it prevents
> useful features from working. Still not too important though.
>
I'll give this one a shot as well, but I'm not yet sure I'm up to it -
will have to look at the code first. :)
--
Mvh. / Best regards
Jesper Juhl - jju@dif.dk
next prev parent reply other threads:[~2002-02-26 11:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-26 11:37 Barubary
2002-02-26 11:54 ` Jesper Juhl [this message]
2002-02-26 12:01 ` Rainer Ellinger
2002-02-26 12:08 ` Barubary
2002-02-26 12:17 ` Change that to an NTFS bug not loopback Barubary
2002-02-27 0:03 ` Richard Russon
2002-02-26 12:04 ` ISO9660 bug and loopback driver bug Alan Cox
2002-02-26 12:02 ` Barubary
2002-02-26 12:37 ` Alan Cox
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=1014724445.5666.2.camel@jju_lnx \
--to=jju@dif.dk \
--cc=barubary@cox.net \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®