| 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
| ||
|
Date: Mon, 16 Jan 2023 15:18:26 +0800
From: kernel test robot <yujie.liu@...el.com>
To: David Howells <dhowells@...hat.com>
CC: <oe-lkp@...ts.linux.dev>, <lkp@...el.com>,
Al Viro <viro@...iv.linux.org.uk>,
<linux-block@...r.kernel.org>,
<v9fs-developer@...ts.sourceforge.net>,
<linux-fsdevel@...r.kernel.org>, <ceph-devel@...r.kernel.org>,
<nvdimm@...ts.linux.dev>, <linux-ext4@...r.kernel.org>,
<linux-f2fs-devel@...ts.sourceforge.net>,
<linux-xfs@...r.kernel.org>,
<jfs-discussion@...ts.sourceforge.net>,
<linux-nfs@...r.kernel.org>, <linux-nilfs@...r.kernel.org>,
<ntfs3@...ts.linux.dev>, <ocfs2-devel@....oracle.com>,
<devel@...ts.orangefs.org>, <reiserfs-devel@...r.kernel.org>
Subject: [dhowells-fs:iov-extract] [iov_iter] 64ea9d6c5f:
xfstests.btrfs.020/026/215.fail
Greeting,
Please note this report is for the v4 patch at
https://lore.kernel.org/r/167305163159.1521586.9460968250704377087.stgit@warthog.procyon.org.uk/
Since v5 has been posted, this report is for your reference only.
We noticed xfstests.btrfs.020/026/215.fail due to commit (built with gcc-11):
commit: 64ea9d6c5f473c29c5de97abaa697856db90fef7 ("iov_iter: Use IOCB/IOMAP_WRITE if available rather than iterator direction")
https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git iov-extract
in testcase: xfstests
version: xfstests-x86_64-fb6575e-1_20230102
with following parameters:
disk: 6HDD
fs: btrfs
test: btrfs-group-02
test-description: xfstests is a regression test suite for xfs and other files ystems.
test-url: git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git
on test machine: 8 threads 1 sockets Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz (Haswell) with 8G memory
caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
btrfs/020 [failed, exit status 1]
btrfs/026 - output mismatch (see /lkp/benchmarks/xfstests/results//btrfs/026.out.bad)
--- tests/btrfs/026.out 2023-01-02 16:54:41.000000000 +0000
+++ /lkp/benchmarks/xfstests/results//btrfs/026.out.bad 2023-01-15 04:49:37.182778590 +0000
@@ -8,8 +8,8 @@
wrote 268435456/268435456 bytes at offset 3145728
XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
File digests before remounting the file system:
-647d815906324ccdf288c7681f900ec0 SCRATCH_MNT/foo
-5876dba1217b4c2915cda86f4c67640e SCRATCH_MNT/bar
+2106fb59f7a6292fbb35cf2fc69f74f9 SCRATCH_MNT/foo
+aca351b2f0529ab0cce383d7e43127d8 SCRATCH_MNT/bar
...
(Run 'diff -u /lkp/benchmarks/xfstests/tests/btrfs/026.out /lkp/benchmarks/xfstests/results//btrfs/026.out.bad' to see the entire diff)
btrfs/215 [failed, exit status 1]- output mismatch (see /lkp/benchmarks/xfstests/results//btrfs/215.out.bad)
--- tests/btrfs/215.out 2023-01-02 16:54:41.000000000 +0000
+++ /lkp/benchmarks/xfstests/results//btrfs/215.out.bad 2023-01-14 18:15:13.161797311 +0000
@@ -1,2 +1,3 @@
QA output created by 215
-Silence is golden
+Errors: 0 expected: 2
+(see /lkp/benchmarks/xfstests/results//btrfs/215.full for details)
...
(Run 'diff -u /lkp/benchmarks/xfstests/tests/btrfs/215.out /lkp/benchmarks/xfstests/results//btrfs/215.out.bad' to see the entire diff)
In addition to that, the commit also has impact on the following tests:
testcase: xfstests
fs: xfs
test: xfs-group-54
2023-01-13 21:25:49 mkfs -t xfs -f -mreflink=0 /dev/sdb1
Metadata corruption detected at 0x43f4b8, xfs_agf block 0x8/0x1000
Metadata corruption detected at 0x43f4b8, xfs_agf block 0x6400008/0x1000
Metadata corruption detected at 0x43f4b8, xfs_agf block 0xc800008/0x1000
Metadata corruption detected at 0x43f4b8, xfs_agf block 0x12c00008/0x1000
Metadata corruption detected at 0x4519d8, xfs_agi block 0x10/0x1000
Metadata corruption detected at 0x4519d8, xfs_agi block 0x6400010/0x1000
Metadata corruption detected at 0x4519d8, xfs_agi block 0xc800010/0x1000
Metadata corruption detected at 0x4519d8, xfs_agi block 0x12c00010/0x1000
Metadata corruption detected at 0x44a3f0, xfs_finobt block 0x38/0x1000
mkfs.xfs: Inode allocation failed [117 - Structure needs cleaning]
meta-data=/dev/sdb1 isize=512 agcount=4, agsize=13107200 blks
= sectsz=4096 attr=2, projid32bit=1
= crc=1 finobt=1, sparse=1, rmapbt=0
= reflink=0 bigtime=0
data = bsize=4096 blocks=52428800, imaxpct=25
= sunit=0 swidth=0 blks
naming =version 2 bsize=4096 ascii-ci=0, ftype=1
log =internal log bsize=4096 blocks=25600, version=2
= sectsz=4096 sunit=1 blks, lazy-count=1
realtime =none extsz=4096 blocks=0, rtextents=0
If you fix the issue, kindly add following tag
| Reported-by: kernel test robot <yujie.liu@...el.com>
| Link: https://lore.kernel.org/oe-lkp/202301161453.f0e8c3a7-yujie.liu@intel.com
To reproduce:
git clone https://github.com/intel/lkp-tests.git
cd lkp-tests
sudo bin/lkp install job.yaml # job file is attached in this email
bin/lkp split-job --compatible job.yaml # generate the yaml file for lkp run
sudo bin/lkp run generated-yaml-file
# if come across any failure that blocks the test,
# please remove ~/.lkp and /lkp dir to run from a clean state.
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
View attachment "config-6.2.0-rc2-00206-g64ea9d6c5f47" of type "text/plain" (172072 bytes)
View attachment "job-script" of type "text/plain" (5863 bytes)
Download attachment "dmesg.xz" of type "application/x-xz" (44772 bytes)
View attachment "xfstests" of type "text/plain" (1903 bytes)
View attachment "job.yaml" of type "text/plain" (4808 bytes)
View attachment "reproduce" of type "text/plain" (1015 bytes)
Powered by blists - more mailing lists