From: "Steven J. Magnani" <steve@digidescorp.com>
To: Stevie Trujillo <stevie.trujillo@gmail.com>
Cc: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>,
linux-kernel@vger.kernel.org
Subject: Re: mount -o loop with truncated dosdisk.img uses 100% cpu and can't be killed
Date: Thu, 12 Jul 2012 10:16:46 -0500 [thread overview]
Message-ID: <1342106206.2156.2.camel@iscandar.digidescorp.com> (raw)
In-Reply-To: <20120712162828.3f561315@localhost>
On Thu, 2012-07-12 at 16:28 +0200, Stevie Trujillo wrote:
> Hello,
>
> I was trying to create a bootdisk to update my BIOS, and accidentially
> made a 512byte image with only the FreeDOS header in it.
>
> ( Linux 3.4.4 )
> # mount -o loop dosdisk.img /tmp
> ^C^C^C
> It uses 100% CPU and doesn't listen to me when I do ^C, kill -9 etc. I
> think this means it's stuck in the kernel?
Here is the stack trace I get for the mount process:
[root@telezart smagnani]# cat /proc/1334/stack
[<ffffffff81077a5a>] __cond_resched+0x2a/0x40
[<ffffffff8110c4bb>] find_lock_page+0x3b/0x80
[<ffffffff8110cbaf>] find_or_create_page+0x3f/0xb0
[<ffffffff8119a692>] __getblk+0xf2/0x2a0
[<ffffffff8119a893>] __bread+0x13/0xb0
[<ffffffffa00fd1fe>] fat__get_entry+0x14e/0x220 [fat]
[<ffffffffa00fd596>] fat_get_short_entry+0x66/0xc0 [fat]
[<ffffffffa00ff765>] fat_subdirs+0x55/0x80 [fat]
[<ffffffffa0103d30>] fat_fill_super+0x810/0xa80 [fat]
[<ffffffffa00e821a>] vfat_fill_super+0x1a/0x20 [vfat]
[<ffffffff8116d61b>] mount_bdev+0x1cb/0x210
[<ffffffffa00e81f5>] vfat_mount+0x15/0x20 [vfat]
[<ffffffff8116e410>] mount_fs+0x20/0xd0
[<ffffffff81186e4f>] vfs_kern_mount+0x6f/0x100
[<ffffffff81187804>] do_kern_mount+0x54/0x110
[<ffffffff811891d6>] do_mount+0x306/0x8b0
[<ffffffff811898cd>] sys_mount+0x8d/0xe0
[<ffffffff81583629>] system_call_fastpath+0x16/0x1b
[<ffffffffffffffff>] 0xffffffffffffffff
I would think this is more likely a bug in the loopback driver than the
FAT filesystem...
------------------------------------------------------------------------
Steven J. Magnani "I claim this network for MARS!
www.digidescorp.com Earthling, return my space modulator!"
#include <standard.disclaimer>
next prev parent reply other threads:[~2012-07-12 15:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-12 14:28 mount -o loop with truncated dosdisk.img uses 100% cpu and can't be killed Stevie Trujillo
2012-07-12 15:16 ` Steven J. Magnani [this message]
2012-07-12 19:21 ` OGAWA Hirofumi
2012-07-12 19:39 ` Steven J. Magnani
2012-07-12 19:49 ` OGAWA Hirofumi
2012-07-13 15:43 ` Jan Kara
2012-07-13 15:52 ` Jeff Moyer
2012-07-13 20:51 ` Jeff Moyer
-- strict thread matches above, loose matches on Subject: below --
2012-07-13 9:18 Wolfram Gloger
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=1342106206.2156.2.camel@iscandar.digidescorp.com \
--to=steve@digidescorp.com \
--cc=hirofumi@mail.parknet.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=stevie.trujillo@gmail.com \
/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