From: Jeff Moyer <jmoyer@redhat.com>
To: Jan Kara <jack@suse.cz>
Cc: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>,
"Steven J. Magnani" <steve@digidescorp.com>,
Stevie Trujillo <stevie.trujillo@gmail.com>,
linux-kernel@vger.kernel.org, Jens Axboe <axboe@kernel.dk>
Subject: Re: mount -o loop with truncated dosdisk.img uses 100% cpu and can't be killed
Date: Fri, 13 Jul 2012 16:51:55 -0400 [thread overview]
Message-ID: <x49y5mn1j10.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <20120713154354.GD28715@quack.suse.cz> (Jan Kara's message of "Fri, 13 Jul 2012 17:43:54 +0200")
Jan Kara <jack@suse.cz> writes:
>> It looks like the bug of __getblk_slow(). If requested block was beyond
>> end of device, __find_get_block() will find buffer_mapped()'s buffer,
>> but block >= end_block is unmapped. So, it can be loop.
>>
>> The following patch fixes it? If it fix, there are some options to check
>> it.
>>
>> a) Check it like this patch and warn.
>> b) (a), but without warn.
>> c) Check it in init_page_buffers() and return -EIO or such
>>
>> Well, anyway, Cc to Jens.
>>
>> Signed-off-by: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
> I think Jeff Moyer has sent a similar fix recently. It may even be
> already queued in Jens' tree. Jeff?
A fix for this has now been committed in Linus' tree:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=91f68c89d8f35fe98ea04159b9a3b42d0149478f
Cheers,
Jeff
next prev parent reply other threads:[~2012-07-13 20:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-12 14:28 Stevie Trujillo
2012-07-12 15:16 ` 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 [this message]
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=x49y5mn1j10.fsf@segfault.boston.devel.redhat.com \
--to=jmoyer@redhat.com \
--cc=axboe@kernel.dk \
--cc=hirofumi@mail.parknet.co.jp \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=steve@digidescorp.com \
--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
all inboxes | Powered by JetHome®