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: Thu, 1 Mar 2001 17:21:45 +0100 [thread overview]
Message-ID: <20010301172145.T21518@suse.de> (raw)
In-Reply-To: <3A9E66BB.70FB0C75@eikon.tum.de>
In-Reply-To: <3A9E66BB.70FB0C75@eikon.tum.de>; from ario@eikon.tum.de on Thu, Mar 01, 2001 at 04:11:55PM +0100
[-- Attachment #1: Type: text/plain, Size: 350 bytes --]
On Thu, Mar 01 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.
--
Jens Axboe
[-- Attachment #2: loop-b_dev-1 --]
[-- Type: text/plain, Size: 435 bytes --]
--- /opt/kernel/linux-2.4.2-ac7/drivers/block/loop.c Thu Mar 1 15:46:14 2001
+++ drivers/block/loop.c Thu Mar 1 17:17:13 2001
@@ -397,10 +397,10 @@
if (!buffer_locked(rbh))
BUG();
- if (MINOR(rbh->b_dev) >= max_loop)
+ if (MINOR(rbh->b_rdev) >= max_loop)
goto out;
- lo = &loop_dev[MINOR(rbh->b_dev)];
+ lo = &loop_dev[MINOR(rbh->b_rdev)];
spin_lock_irq(&lo->lo_lock);
if (lo->lo_state != Lo_bound)
goto inactive;
next prev parent reply other threads:[~2001-03-01 16:22 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 [this message]
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
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=20010301172145.T21518@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