From: "Barubary" <barubary@cox.net>
To: "Rainer Ellinger" <rainer@ellinger.de>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: ISO9660 bug and loopback driver bug
Date: Tue, 26 Feb 2002 04:08:08 -0800 [thread overview]
Message-ID: <009c01c1bebe$41321730$a7eb0544@CX535256D> (raw)
In-Reply-To: <006001c1beb9$ea412690$a7eb0544@CX535256D> <3C7B7908.1040508@ellinger.de>
Can you try a file between 2^31 and 2^32-1, inclusive? Maybe it's a
sign-related bug in the loopback driver, not a 64 bit I/O bug.
The file I tried to mount is this on an NTFS partition:
12/10/2001 20:13 3,522,562,048 dvd.iso
"losetup" fails too, meaning it's the loopback driver (and possibly the NTFS
driver) that is glitching, not the ISO driver.
Maybe trying to mount *anything* from an NTFS driver doesn't work? I'll
have to check that possibility too...
-- Barubary
----- Original Message -----
From: "Rainer Ellinger" <rainer@ellinger.de>
To: "Barubary" <barubary@cox.net>
Cc: <linux-kernel@vger.kernel.org>
Sent: Tuesday, February 26, 2002 4:01 AM
Subject: Re: ISO9660 bug and loopback driver bug
> Barubary wrote:
>
> > Now the loopback bug. Files whose size is greater than 2^31-1 don't
work
> > with the loopback driver.
>
> Can't reproduce. I can mount 4.7GB DVD-Images and i'm currently working
with an 48GB File mounted via loop, and a 100GB partition
> mounted via loop. I'm using loop-AES encryption patch with 2.4.17/18-rc4.
I'm not aware if there's a fix in this patch. afaik it
> should also work with vanilla loop.c.
>
> --
> rainer@ellinger.de
>
>
next prev parent reply other threads:[~2002-02-26 12:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-26 11:37 ISO9660 bug and loopback driver bug Barubary
2002-02-26 11:54 ` Jesper Juhl
2002-02-26 12:01 ` Rainer Ellinger
2002-02-26 12:08 ` Barubary [this message]
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='009c01c1bebe$41321730$a7eb0544@CX535256D' \
--to=barubary@cox.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rainer@ellinger.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.