From: Jari Ruusu <jariruusu@users.sourceforge.net>
To: Ruben Garcia <ruben@ugr.es>
Cc: linux-kernel@vger.kernel.org
Subject: Re: loop device changes the block size and causes misaligned accessesto the real device, which can't be processed
Date: Wed, 07 Jan 2004 20:12:01 +0200 [thread overview]
Message-ID: <3FFC4BF1.B6A5ADAE@users.sourceforge.net> (raw)
In-Reply-To: 3FFC3BF4.6080105@ugr.es
Ruben Garcia wrote:
> The loop device advertises a block size of 1024 even when configured
> over a cdrom.
This bug and many other loop bugs are fixed in loop-AES package.
http://loop-aes.sourceforge.net/loop-AES/loop-AES-v2.0d.tar.bz2
--
Jari Ruusu 1024R/3A220F51 5B 4B F9 BB D3 3F 52 E9 DB 1D EB E3 24 0E A9 DD
next prev parent reply other threads:[~2004-01-07 18:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-07 17:03 loop device changes the block size and causes misaligned accesses to the real device, which can't be processed Ruben Garcia
2004-01-07 18:12 ` Jari Ruusu [this message]
2004-01-12 4:12 ` loop device changes the block size and causes misaligned accessesto " Bill Davidsen
2004-01-08 4:04 ` [PATCH] Re: loop device changes the block size and causes misaligned accesses to " Ben Slusky
2004-01-08 10:45 ` Ruben Garcia
2004-01-12 14:12 ` Ruben Garcia
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=3FFC4BF1.B6A5ADAE@users.sourceforge.net \
--to=jariruusu@users.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=ruben@ugr.es \
/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.