linux-kernel - Re: file corruption in loop device in 3.4.0

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] [day] [month] [year] [list]

Date:	Wed, 6 Jun 2012 22:48:38 +0800
From:	Ming Lei <tom.leiming@...il.com>
To:	Bob Sullivan <bobsullivan60@...oo.com>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: file corruption in loop device in 3.4.0

On Wed, Jun 6, 2012 at 10:24 PM, Bob Sullivan <bobsullivan60@...oo.com> wrote:
> We have a EXT3 filesystem contained in a file
> (a disk image mapped to a file using loop device).
> Using diff, observed random differences between
> files on the image and a backup copies of those files.
> This problem is reproducible,
> tried booting several times with 3.3.8 and 3.4.0.
> No problems on 3.3.8.

A bit different with me, no problems on 3.4, but have problems on 3.5-rc1.

I can easily reproduce the problem, just kernel boot and mount
rootfs(ext4), then
reboot again and found there are many rootfs errors as below, see attachment
for fsck check result.

[   22.451385] EXT4-fs error (device mmcblk0p2):
ext4_mb_generate_buddy:741: group 2, 0 clusters in bitmap, 1 in gd
[   23.263092] JBD2: Spotted dirty metadata buffer (dev = mmcblk0p2,
blocknr = 0). There's a risk of filesystem corruption in case of
system crash.

BTW: I use mmc card to store rootfs and test it on OMAP3 based beagle-xm board.

Thanks,
-- 
Ming Lei

View attachment "ext4.txt" of type "text/plain" (10265 bytes)