mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andries Brouwer <aebr@win.tue.nl>
To: Chris Spiegel <lkml@happyjack.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Oops with loop devices on 2.6.9
Date: Sun, 14 Nov 2004 23:04:31 +0100	[thread overview]
Message-ID: <20041114220431.GA20151@pclin040.win.tue.nl> (raw)
In-Reply-To: <20041112104934.GA1711@midgard.comcast.net>

On Fri, Nov 12, 2004 at 02:49:34AM -0800, Chris Spiegel wrote:

>   While playing around with loop mounts on kernel 2.6.9 I managed to get
> a kernel panic.  After messing around with it I can reproduce the
> problem reliably.  The sequence I came up with to cause the problem:
> 
> mount -o loop /dev/loop/0 /mnt
> mount -o loop /dev/loop/1 /mnt
> mount -o loop /dev/loop/2 /mnt
> mount /dev/loop/0 /mnt -t ext2
> 
> Unable to handle kernel paging request at virtual address 98858a6f
>  printing eip:
> c011345a
> *pde = 00000000
> Oops: 0000 [#1]
> SMP
> Modules linked in:
> CPU     0
> EIP     0060:[<c011345a>]    Not tainted VLI
> EFLAGS  00010083   (2.6.9)
> EIP is at do_page_fault+0x99/0x599
> eax: c9100000   ebx: 65642f3c   ecx: 0000007b   edx: f7d4858b
> esi: 00000000   edi: c01133c1   ebp: 988589ff   esp: c9100108
> ds: 007b   es: 007b   ss: 0068
> Unable to handle kernel NULL pointer dereference at virtual address 00000070
>  printing eip:
> c011345a
> *pde = 00000000

I do not see precisely the same - but I do not use devfs.
What happens for me is: the "mount -o loop /dev/loop0 /mnt"
takes the first unused loop device, /dev/loop0, and then
does "losetup /dev/loop0 /dev/loop0", and then does mount.
But there is a loop in the loop devices and the kernel dies in
infinite recursion.

The easiest fix is saying "don't do that then".
But, on the other hand, maybe it is reasonable to add a check.
Hope to send a patch later this evening.

Andries

      reply	other threads:[~2004-11-14 22:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-12 10:49 Chris Spiegel
2004-11-14 22:04 ` Andries Brouwer [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=20041114220431.GA20151@pclin040.win.tue.nl \
    --to=aebr@win.tue.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@happyjack.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

all inboxes | Powered by JetHome®