From: Miklos Szeredi <mszeredi@inf.bme.hu>
To: Eduard Bloch <blade@debian.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [HOWTO...] LUFS, readpage and large files
Date: Fri, 4 Jun 2004 18:46:11 +0200 (MET DST) [thread overview]
Message-ID: <200406041646.i54GkB125696@kempelen.iit.bme.hu> (raw)
> while writting a new LUFS plugin (to emulate large file support on
> FAT32;) I stumbled over a problem with it's kernel communication module.
> The symptoms were the same as with broken programs that use int or long
> int instead of size_t (or even long long) for storing file offsets.
> However, here the broken offsets (modulo 4GB) came from kernel so I
> traced it down to this method:
[...]
> offset = p->index << PAGE_CACHE_SHIFT;
This should be:
offset = (unsigned long long) p->index << PAGE_CACHE_SHIFT;
BTW, you can use FUSE + LUFIS for running LUFS filesystems with the
FUSE kernel module. Or even better: you can write your filesystem
natively with FUSE ;)
You can download LUFIS from http://sourceforge.net/projects/avf, FUSE
is already in debian testing.
Cheers,
Miklos
next reply other threads:[~2004-06-04 16:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-04 16:46 Miklos Szeredi [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-04 15:51 Eduard Bloch
2004-06-05 4:50 ` Andrew Morton
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=200406041646.i54GkB125696@kempelen.iit.bme.hu \
--to=mszeredi@inf.bme.hu \
--cc=blade@debian.org \
--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®