All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ruben Garcia <ruben@ugr.es>
To: unlisted-recipients:; (no To-header on input)
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Re: loop device changes the block size and causes misaligned accesses to the real device, which can't be processed
Date: Mon, 12 Jan 2004 15:12:55 +0100	[thread overview]
Message-ID: <4002AB67.3010005@ugr.es> (raw)
In-Reply-To: <3FFD34D5.1080605@ugr.es>

Ruben Garcia wrote:
> Ok, Ben's patch will make the loop device work as any other device, and 
> then ext2 will complain that the hard blocksize is bigger than the 
> blocksize used for ext2 (in my example of 1k for ext2) and fail to mount 
> it.
> 
> This is better than getting misaligned transfers et all, and is 
> consistent with using the real device.
> 
> On the other hand, it is much more useful being able to actually mount 
> the ext2 fs, and I managed to do that with the loop-aes patch (Thanks 
> Jari Ruusu)
> 
> I confirm this bug closed. Thanks to all
>

I tried Ben's patch and it does work for encrypted CDs (i.e. you can 
mount them) I'm going to try a non encrypted CD now to see what I find.


      reply	other threads:[~2004-01-12 14: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 ` loop device changes the block size and causes misaligned accessesto " Jari Ruusu
2004-01-12  4:12   ` 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 [this message]

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=4002AB67.3010005@ugr.es \
    --to=ruben@ugr.es \
    --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 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.