linux-kernel - [lkp-robot] [ext4] 3fbc7bbd07: kmsg.EXT4-fs_error(device_sda2):ext4_validate:#:inode##:comm_blogbench:bad_nlink

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:   Mon, 23 Jan 2017 09:23:58 +0800
From:   kernel test robot <xiaolong.ye@...el.com>
To:     yi zhang <yi.zhang@...wei.com>
Cc:     linux-ext4@...r.kernel.org, linux-fsdevel@...r.kernel.org,
        linux-kernel@...r.kernel.org, tytso@....edu,
        adilger.kernel@...ger.ca, viro@...IV.linux.org.uk,
        yi.zhang@...wei.com, lkp@...org
Subject: [lkp-robot] [ext4]  3fbc7bbd07:
 kmsg.EXT4-fs_error(device_sda2):ext4_validate:#:inode##:comm_blogbench:bad_nlink_value


FYI, we noticed the following commit:

commit: 3fbc7bbd071c2fa802d94aab68257ee591ff2185 ("ext4: add detection of i_nlink")
url: https://github.com/0day-ci/linux/commits/yi-zhang/vfs-add-detection-of-inode-validation/20170119-013142
base: https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git dev

in testcase: blogbench
with following parameters:

	disk: 1HDD
	fs: ext4
	cpufreq_governor: performance

test-description: Blogbench is a portable filesystem benchmark that tries to reproduce the load of a real-world busy file server.
test-url: https://www.pureftpd.org/project/blogbench


on test machine: 32 threads Intel(R) Core(TM) i5-2300 CPU @ 2.80GHz with 4G memory

caused below changes:


[   23.891025] Benchmarking for 30 iterations.
[   23.891027] 
[   23.898537] The test will run during 5 minutes.
[   23.898538] 
[   23.905748] 
[   23.909450]   Nb blogs   R articles    W articles    R pictures    W pictures    R comments    W comments
[   23.909451] 
[   25.439956] EXT4-fs error (device sda2): ext4_validate:5388: inode #35127453: comm blogbench: bad nlink value: 0
[   25.474247] EXT4-fs error (device sda2): ext4_validate:5388: inode #35127453: comm blogbench: bad nlink value: 0
[   26.239439] EXT4-fs error (device sda2): ext4_validate:5388: inode #45088934: comm blogbench: bad nlink value: 0
[   26.277307] EXT4-fs error (device sda2): ext4_validate:5388: inode #45088934: comm blogbench: bad nlink value: 0
[   33.845065]        144      1367458          7950        874822          7055        698873         23004
[   33.845071] 
[   34.567113] EXT4-fs error (device sda2): ext4_validate:5388: inode #38797366: comm blogbench: bad nlink value: 0
[   36.457183] EXT4-fs error (device sda2): ext4_validate:5388: inode #1835048: comm blogbench: bad nlink value: 0
[   36.541966] EXT4-fs error (device sda2): ext4_validate:5388: inode #1835048: comm blogbench: bad nlink value: 0
[   36.590946] EXT4-fs error (device sda2): ext4_validate:5388: inode #1835048: comm blogbench: bad nlink value: 0
[   36.708818] EXT4-fs error (device sda2): ext4_validate:5388: inode #1835048: comm blogbench: bad nlink value: 0
[   36.717562] EXT4-fs error (device sda2): ext4_validate:5388: inode #1835048: comm blogbench: bad nlink value: 0
[   36.737046] EXT4-fs error (device sda2): ext4_validate:5388: inode #1835048: comm blogbench: bad nlink value: 0
[   36.857064] EXT4-fs error (device sda2): ext4_validate:5388: inode #1835048: comm blogbench: bad nlink value: 0
[   36.886975] EXT4-fs error (device sda2): ext4_validate:5388: inode #1835048: comm blogbench: bad nlink value: 0
[   37.050375] EXT4-fs error (device sda2): ext4_validate:5388: inode #1835048: comm blogbench: bad nlink value: 0
[   39.914724] EXT4-fs error: 26 callbacks suppressed
[   39.920397] EXT4-fs error (device sda2): ext4_validate:5388: inode #14418082: comm blogbench: bad nlink value: 0
[   39.941975] EXT4-fs error (device sda2): ext4_validate:5388: inode #14418082: comm blogbench: bad nlink value: 0
[   39.956585] EXT4-fs error (device sda2): ext4_validate:5388: inode #14680188: comm blogbench: bad nlink value: 0
[   39.959336] EXT4-fs error (device sda2): ext4_validate:5388: inode #14418082: comm blogbench: bad nlink value: 0
[   39.969813] EXT4-fs error (device sda2): ext4_validate:5388: inode #14418082: comm blogbench: bad nlink value: 0
[   39.971726] EXT4-fs error (device sda2): ext4_validate:5388: inode #20316356: comm blogbench: bad nlink value: 0
[   39.973644] EXT4-fs error (device sda2): ext4_validate:5388: inode #14418082: comm blogbench: bad nlink value: 0
[   39.990417] EXT4-fs error (device sda2): ext4_validate:5388: inode #27000844: comm blogbench: bad nlink value: 0
[   39.993916] EXT4-fs error (device sda2): ext4_validate:5388: inode #27000844: comm blogbench: bad nlink value: 0
[   40.019657] EXT4-fs error (device sda2): ext4_validate:5388: inode #27000844: comm blogbench: bad nlink value: 0
[   43.844343]        172      1222347          1446        783841          1404        774376          6563




To reproduce:

        git clone git://git.kernel.org/pub/scm/linux/kernel/git/wfg/lkp-tests.git
        cd lkp-tests
        bin/lkp install job.yaml  # job file is attached in this email
        bin/lkp run     job.yaml



Thanks,
Xiaolong

View attachment "config-4.10.0-rc3-00016-g3fbc7bb" of type "text/plain" (155604 bytes)

View attachment "job-script" of type "text/plain" (6870 bytes)

Download attachment "dmesg.xz" of type "application/octet-stream" (19420 bytes)

View attachment "blogbench" of type "text/plain" (3246 bytes)

View attachment "job.yaml" of type "text/plain" (4549 bytes)

View attachment "reproduce" of type "text/plain" (254 bytes)