All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Collier <Ian.Collier@comlab.ox.ac.uk>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.13: loop ioctl crashes
Date: Fri, 9 Sep 2005 16:42:47 +0100	[thread overview]
Message-ID: <20050909164246.B23692@pixie.comlab> (raw)
In-Reply-To: <Pine.LNX.4.61.0509091017020.4550@chaos.analogic.com>; from linux-os@analogic.com on Fri, Sep 09, 2005 at 10:41:29AM -0400

On Fri, Sep 09, 2005 at 10:41:29AM -0400, linux-os (Dick Johnson) wrote:
> Try to see if it is really the loop device or something that is
> interfacing with it. Here I copy the contents of a DOS floppy
> to a file, then mount the file through the loop device:

I do know how to use loop devices. ;-)

Now you mention it, "losetup" without encryption works fine.

This: losetup -e blowfish /dev/loop0 /tmp/test.img
fails with "bad address" if the blowfish module is not loaded,
and causes a kernel panic if it is (and now I have to go home
to reset my machine. :-( ).

The only thing I can see that the ppdd patch has done here is to
increase LO_KEY_SIZE from 32 to 1844; the rest should be as in
vanilla 2.6.13 (though at some point I'll recompile without
patches and see if that changes anything).

imc

  parent reply	other threads:[~2005-09-09 15:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-09 12:27 2.6.13: loop ioctl crashes Ian Collier
2005-09-09 12:32 ` linux-os (Dick Johnson)
2005-09-09 13:38   ` Ian Collier
2005-09-09 14:41     ` linux-os (Dick Johnson)
2005-09-09 14:59       ` linux-os (Dick Johnson)
2005-09-09 15:42       ` Ian Collier [this message]
2005-09-14 12:51 ` 2.6.13: More on drivers/block/loop.c Ian Collier
2005-09-14 13:12   ` Anton Altaparmakov
2005-09-14 15:38 ` loop: auto-load crypto module [PATCH] Ian Collier

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=20050909164246.B23692@pixie.comlab \
    --to=ian.collier@comlab.ox.ac.uk \
    --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.