linux-kernel - Re: [lkp] [btrfs] 164a91c9be: xfstests.generic.088.fail

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:	Tue, 21 Jun 2016 18:25:00 +0800
From:	Anand Jain <anand.jain@...cle.com>
To:	kernel test robot <xiaolong.ye@...el.com>
Cc:	0day robot <fengguang.wu@...el.com>,
	LKML <linux-kernel@...r.kernel.org>, lkp@...org
Subject: Re: [lkp] [btrfs] 164a91c9be: xfstests.generic.088.fail



Thanks for the report.

 > _check_btrfs_filesystem: filesystem on /dev/sda5 is inconsistent (see 
/lkp/benchmarks/xfstests/results//check.full)
 > generic/088	 0s

Ran tests again unfortunately I couldn't reproduce..
---------
generic/088 0s ... 0s
generic/089 21s ... 39s
generic/090 4s ... 4s
generic/091 58s ... 58s
generic/092 1s ... 0s
generic/096	 [not run] xfs_io fzero failed (old kernel/wrong fs?)
generic/098 2s ... 2s
generic/100 18s ... 18s
generic/101	 3s
generic/102	 8s
generic/103	 2s
----------

But a possible scenario .. in systems where rcu_callback itself
could be deferred it needs rcu_barrier(). Fixed this in V2, by
restoring rcu_barrier() and then grace period wait for devices
to close.


>     +mount: /dev/sda6 is already mounted or /fs/scratch busy
::
>     +umount: /dev/sda6: not mounted

This might be different issue, when this happens generally
wipefs all scratch pool devices helps.


Thanks, Anand