public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mario Hermann <ario@eikon.tum.de>
To: Jens Axboe <axboe@suse.de>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: report bug: System reboots when accessing a loop-device over a  second loop-device with 2.4.2-ac7
Date: Fri, 02 Mar 2001 18:50:56 +0100	[thread overview]
Message-ID: <3A9FDD80.FD075386@eikon.tum.de> (raw)
In-Reply-To: <3A9E66BB.70FB0C75@eikon.tum.de> <20010301172145.T21518@suse.de> <3A9FADAB.F37E5449@eikon.tum.de> <20010302162824.H408@suse.de>

Hello!

Jens Axboe wrote:
> 
> On Fri, Mar 02 2001, Mario Hermann wrote:
> > There is another small bug with the loop over loop problem. Now it works
> > fine for
> > files but not for Devices:
> >
> > losetup /dev/loop0 /dev/sr1
> > losetup /dev/loop1 /dev/loop0
> > dd if=/dev/loop1 of=test.dat bs=2048 count=1024
> 
> Pending miscount, this should fix it.


Ok, I did some testing again. What I found:

Without crypto: Everything works good!

With crypto:

I used the ciphers: idea,serbent, aes, blowfish(with small patch in
cipher-blowfish send somewhere in the past)

Only 2.4.2-ac8 Material: Everything is ok. 

With  old 2.2-Material:

Encrypted in the way: 

 losetup -e blowfish /dev/loop0 ./test.file
 losetup -e serpent /dev/loop1 /dev/loop0

It works perfect too! :-)

But with old 2.2 - Material stored on DVD-RAM. 

  losetup -e blowfish /dev/loop0 /dev/sr3
  lsoetup -e serpent /dev/loop1 /dev/loop0

it doesn't work.

Just garbage comes out of the loop-device.
Both, the file on the harddisk and the DVD-RAM are made with 2.2.16 an
patch-int-2.2.16.9 and are working
there perfectly. 

I guess that the problem has maybe something to do with the logical
block number.

Well, for me was the HD-File important to work under 2.4 (DB-on it...)

So great thx from me!

Hope my testing will help in some way. (will do some more monday
afternoon)


---
Mario Hermann

  reply	other threads:[~2001-03-02 20:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-01 15:11 report bug: System reboots when accessing a loop-device over a second loop-device with 2.4.2-ac7 Mario Hermann
2001-03-01 15:22 ` Jens Axboe
2001-03-01 16:21 ` Jens Axboe
2001-03-01 17:00   ` Mario Hermann
2001-03-02 14:26   ` Mario Hermann
2001-03-02 15:07     ` Jens Axboe
2001-03-02 15:28     ` Jens Axboe
2001-03-02 17:50       ` Mario Hermann [this message]
2001-03-03  3:19         ` Jens Axboe

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=3A9FDD80.FD075386@eikon.tum.de \
    --to=ario@eikon.tum.de \
    --cc=axboe@suse.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox