From: Andreas Dilger <adilger@turbolinux.com>
To: Ingo Rohloff <rohloff@in.tum.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Loop encryption module locking bug (linux-2.4.5).
Date: Thu, 21 Jun 2001 12:19:16 -0600 (MDT) [thread overview]
Message-ID: <200106211819.f5LIJGqP015476@webber.adilger.int> (raw)
In-Reply-To: <20010621135043.A13107@lxmayr6.informatik.tu-muenchen.de> "from Ingo Rohloff at Jun 21, 2001 01:50:43 pm"
Ingo Rohloff writes:
> PS: Because I try to understand the inner workings of the loop
> device better, I have a question:
> In lo_send is a loop: "while (len>0)". How can I configure
> a loop device, so that this loop is executed more than once.
> It seems this is only possible if "bh->b_size" is greater
> than PAGE_CACHE_SIZE. Does this mean, you have to work on
> a filesystem which uses blocks of a size > PAGE_CACHE_SIZE,
> or is bh->b_size a fixed value (which is always less than
> PAGE_CACHE_SIZE) ?
Currently, filesystems must have block size <= PAGE_CACHE_SIZE.
This may not be true in the future, so it is likely that the loop
code is "forward looking" to try to still work if the block size
can exceed the PAGE_CACHE_SIZE.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- Dogbert
next prev parent reply other threads:[~2001-06-21 18:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-21 11:50 Ingo Rohloff
2001-06-21 18:19 ` Andreas Dilger [this message]
[not found] <20010621135043.A13107@lxmayr6.informatik.tu-muenchen.de.suse.lists.linux.kernel>
2001-06-21 12:36 ` Andi Kleen
[not found] ` <3B333180.A804582F@pp.inet.fi>
[not found] ` <20010622135942.A1591@gruyere.muc.suse.de>
2001-06-22 15:08 ` Ingo Rohloff
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=200106211819.f5LIJGqP015476@webber.adilger.int \
--to=adilger@turbolinux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rohloff@in.tum.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 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®