From: Jens Axboe <axboe@suse.de>
To: Mario Hermann <ario@eikon.tum.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, 2 Mar 2001 16:07:59 +0100 [thread overview]
Message-ID: <20010302160759.G408@suse.de> (raw)
In-Reply-To: <3A9E66BB.70FB0C75@eikon.tum.de> <20010301172145.T21518@suse.de> <3A9FADAB.F37E5449@eikon.tum.de>
In-Reply-To: <3A9FADAB.F37E5449@eikon.tum.de>; from ario@eikon.tum.de on Fri, Mar 02, 2001 at 03:26:51PM +0100
On Fri, Mar 02 2001, Mario Hermann wrote:
> > > I tried the following commands with 2.4.2-ac7:
> > >
> > > losetup /dev/loop0 test.dat
> > > losetup /dev/loop1 /dev/loop0
> > > mke2fs /dev/loop1
> > >
> > > My System reboots immediatly. I tried it with 2.4.2-ac4,ac5 too -> same
> > > effect.
> > >
> > > With 2.4.2 it hangs immediatly.
> >
> > This should make it work again.
>
> 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
>
> Makes dd hang. (BTW: /dev/sr1 is a CD-ROM)
>
> Tried the same on /dev/hda1, /dev/sda1 with 2.4.2-ac7-your_patch and
> with 2.4.2-ac8.
I must admit that I haven't tried loop-over-loop at all really,
I'll make a note to look at this tonight.
> BTW: Did extensiv testing with and without the crypto patches. And all
> other tests worked fine! :-)
Great.
--
Jens Axboe
next prev parent reply other threads:[~2001-03-02 15:08 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 [this message]
2001-03-02 15:28 ` Jens Axboe
2001-03-02 17:50 ` Mario Hermann
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=20010302160759.G408@suse.de \
--to=axboe@suse.de \
--cc=ario@eikon.tum.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