Re: mount -o loop with truncated dosdisk.img uses 100% cpu and can't be killed

[Jeff Moyer <jmoyer@xxxxxxxxxx>]

Jan Kara <jack@xxxxxxx> 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@xxxxxxxxxxxxxxxxxx>
>   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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/