linux-kernel - Re: mkfs.f2fs gets stuck with "blk_update

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAMo8Bf+83t3ML_Ctr4V-pVL7Meei=pdOeC5cgtrPJB12tOcGtA@mail.gmail.com>
Date:	Tue, 2 Apr 2013 19:41:37 +0400
From:	Max Filippov <jcmvbkbc@...il.com>
To:	slava@...eyko.com
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Jaegeuk Kim <jaegeuk.kim@...sung.com>,
	Jens Axboe <axboe@...nel.dk>,
	linux-f2fs-devel@...ts.sourceforge.net
Subject: Re: mkfs.f2fs gets stuck with "blk_update_request: bio idx 0 >= vcnt
 0" on 3.8

On Tue, Apr 2, 2013 at 10:27 AM, Vyacheslav Dubeyko <slava@...eyko.com> wrote:
> On Tue, 2013-04-02 at 00:21 +0400, Max Filippov wrote:

[...]

>> # cat /proc/partitions
>> major minor  #blocks  name
>>
>>  179        0    7782400 mmcblk0
>>  179        1      40131 mmcblk0p1
>>  179        2      32130 mmcblk0p2
>>  179        3    5685248 mmcblk0p3
>>
>
> As I see, you have several partition on your SD-card. How did it
> prepared?

I made it with fdisk, just as with any other block device.

>> strace output is the following:
>>
> [snip]
>> write(1, "Info: sector size = 512\n", 24) = 24
>> write(1, "Info: total sectors = 11370496 ("..., 45) = 45
>> write(1, "Info: zone aligned segment0 blka"..., 41) = 41
>> fstat64(3, {st_mode=S_IFBLK|0660, st_rdev=makedev(179, 3), ...}) = 0
>> ioctl(3, BLKDISCARD
>
> As I understand, the BLKDISCARD ioctl (to pre-discard all blocks on an
> ssd, or a thinly-provisioned storage device) is a visible reason of the
> issue. Unfortunately, as I see, mkfs.f2fs doesn't support option to
> format partition without blocks discard step.
>
> So, I think that it needs to investigate issue in the direction of
> BLKDISCARD code on the kernel side. It makes sense to debug
> f2fs_trim_device() method of mkfs.f2fs utility too. But I can't see
> anything strange in this function at a glance.

Ok, I'll try to find what has changed in that ioctl handler since 3.6.

-- 
Thanks.
-- Max
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/