From: Stevie Trujillo <stevie.trujillo@gmail.com>
To: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>,
linux-kernel@vger.kernel.org
Subject: mount -o loop with truncated dosdisk.img uses 100% cpu and can't be killed
Date: Thu, 12 Jul 2012 16:28:28 +0200 [thread overview]
Message-ID: <20120712162828.3f561315@localhost> (raw)
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 base64 encoded image (use base64 -d command to unpack it).
6zyQRnJlZURPUyAAAgEBAALgAEAL8AkAEgACAAAAAAAAAAAAAAApOATF6E5PIE5BTUUgICAgRkFU
MTIgICD6/DHAjti9AHy44B+OwInuie+5AAHzpepefOAfAABgAI7YjtCNZqD7gH4k/3UDiFYkx0bA
EADHRsIBAOjpAEZyZWVET1MAi3Yci34eA3YOg9cAiXbSiX7UikYQmPdmFgHGEdeJdtaJftiLXgux
BdPri0YRMdL384lG0AHGg9cAiXbaiX7ci0bWi1bYi37QxF5a6JsAci/Eflq5CwC+8X1X86ZfJotF
GnQLg8cgJoA9AHXncllQxF5ai34Wi0bSi1bU6GsAWHJGHgeOXly/ACCricYB9gHG0e6tcwSxBNPo
gOQPPfgPcugxwKsOH8ReWr4AIK0JwHQkSEiLfg2B5/8A9+cDRtoTVtzoJABz5egXACBlcnIAMOTN
Fs0Zil4k/25aMdu0Ds0QXqxWPAB188NWiUbIiVbKjEbGiV7EtEG7qlWKViSE0nQZzRNyFdHpgdtU
qnUNjXbAiV7MiV7OtELrLItOyItWyopGGPZmGpH38ZL2dhiJ0YjGhunQydDJikYYKOD+xAjhxF7E
uAECilYkzRNzBjDkzRProotGC/Z2wAFGxoNGyAGDVsoAT3XqjkbGXsNLRVJORUwgIFNZUwAAVao=
--
Stevie Trujillo
next reply other threads:[~2012-07-12 14:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-12 14:28 Stevie Trujillo [this message]
2012-07-12 15:16 ` mount -o loop with truncated dosdisk.img uses 100% cpu and can't be killed Steven J. Magnani
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=20120712162828.3f561315@localhost \
--to=stevie.trujillo@gmail.com \
--cc=hirofumi@mail.parknet.co.jp \
--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