From: Jari Ruusu <jari.ruusu@pp.inet.fi>
To: marcelo@conectiva.com.br
Cc: Herbert Valerio Riedel <hvr@hvrlab.org>,
Andrea Arcangeli <andrea@suse.de>,
axboe@suse.de, linux-kernel@vger.kernel.org
Subject: Re: RFC(ry): breaking loop.c's IV calculation
Date: Tue, 04 Dec 2001 00:22:55 +0200 [thread overview]
Message-ID: <3C0BFB3F.9111CD2C@pp.inet.fi> (raw)
In-Reply-To: <3C0A51B0.9AD14E74@pp.inet.fi> <Pine.LNX.4.33.0112021716001.2563-100000@janus.txd.hvrlab.org> <20011202234625.A3447@athlon.random> <1007388763.1674.37.camel@janus.txd.hvrlab.org>
[-- Attachment #1: Type: text/plain, Size: 863 bytes --]
Herbert Valerio Riedel wrote:
> well, I've put one patch together (it still needs (constructive)
> auditing though! jari?) here it is (it's against 2.4.16's loop.[ch])
I have attached my version of loop.c bug fixes. These are extracted from
loop-AES and are well tested.
- IV computed in 512 byte units.
- Make device backed loop work with swap by pre-allocating pages.
- External encryption module locking bug fixed (from Ingo Rohloff).
- Get rid of the loop_get_bs() crap.
- grab_cache_page() return value handled properly, avoids Oops.
- No more illegal messing with BH_Dirty flag.
- No more illegal sleeping in generic_make_request().
- Loops can be set-up properly when root partition is still mounted ro.
- Default soft block size is set properly for file backed loops.
- kmalloc() error case handled properly.
Regards,
Jari Ruusu <jari.ruusu@pp.inet.fi>
[-- Attachment #2: loop-fixes-2.4.17-pre2.diff.gz --]
[-- Type: application/x-gzip, Size: 7182 bytes --]
next prev parent reply other threads:[~2001-12-04 0:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3C0A51B0.9AD14E74@pp.inet.fi>
[not found] ` <Pine.LNX.4.33.0112021716001.2563-100000@janus.txd.hvrlab.org>
[not found] ` <20011202234625.A3447@athlon.random>
2001-12-03 14:12 ` RFC(ry): breaking loop.c's IV calculation Herbert Valerio Riedel
2001-12-03 19:00 ` Jari Ruusu
2001-12-03 22:22 ` Jari Ruusu [this message]
2001-12-04 13:48 ` Herbert Valerio Riedel
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=3C0BFB3F.9111CD2C@pp.inet.fi \
--to=jari.ruusu@pp.inet.fi \
--cc=andrea@suse.de \
--cc=axboe@suse.de \
--cc=hvr@hvrlab.org \
--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 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.