linux-kernel - Re: [linus:master] [btrfs] 8af94e772e: xfstests.btrfs.220.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]

Message-ID: <d188b1ef-5e84-438c-863b-807e534fb67d@gmx.com>
Date: Thu, 5 Jun 2025 08:23:34 +0930
From: Qu Wenruo <quwenruo.btrfs@....com>
To: kernel test robot <oliver.sang@...el.com>, Qu Wenruo <wqu@...e.com>
Cc: oe-lkp@...ts.linux.dev, lkp@...el.com, linux-kernel@...r.kernel.org,
 David Sterba <dsterba@...e.com>, linux-btrfs@...r.kernel.org
Subject: Re: [linus:master] [btrfs] 8af94e772e: xfstests.btrfs.220.fail



在 2025/6/5 00:21, kernel test robot 写道:
> 
> 
> Hello,
> 
> kernel test robot noticed "xfstests.btrfs.220.fail" on:
> 
> commit: 8af94e772ef7bede90895318a3fda6c68a652774 ("btrfs: remove standalone "nologreplay" mount option")

That is fixed by fstests commit: 49170253afef ("fstests: btrfs/220: do 
not use nologreplay when possible"), which is in patches-in-queue branch 
already.

Thanks,
Qu

> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
> 
> [test failed on linus/master      7d4e49a77d9930c69751b9192448fda6ff9100f1]
> [test failed on linux-next/master 3a83b350b5be4b4f6bd895eecf9a92080200ee5d]
> 
> in testcase: xfstests
> version: xfstests-x86_64-e161fc34-1_20250526
> with following parameters:
> 
> 	disk: 6HDD
> 	fs: btrfs
> 	test: btrfs-220
> 
> 
> 
> config: x86_64-rhel-9.4-func
> compiler: gcc-12
> test machine: 8 threads 1 sockets Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz (Haswell) with 8G memory
> 
> (please refer to attached dmesg/kmsg for entire log/backtrace)
> 
> 
> 
> 
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <oliver.sang@...el.com>
> | Closes: https://lore.kernel.org/oe-lkp/202506042235.7e3a37da-lkp@intel.com
> 
> 2025-06-01 10:11:00 export TEST_DIR=/fs/sdb1
> 2025-06-01 10:11:00 export TEST_DEV=/dev/sdb1
> 2025-06-01 10:11:00 export FSTYP=btrfs
> 2025-06-01 10:11:00 export SCRATCH_MNT=/fs/scratch
> 2025-06-01 10:11:00 mkdir /fs/scratch -p
> 2025-06-01 10:11:00 export SCRATCH_DEV_POOL="/dev/sdb2 /dev/sdb3 /dev/sdb4 /dev/sdb5 /dev/sdb6"
> 2025-06-01 10:11:01 echo btrfs/220
> 2025-06-01 10:11:01 ./check btrfs/220
> FSTYP         -- btrfs
> PLATFORM      -- Linux/x86_64 lkp-hsw-d01 6.15.0-rc6-00302-g8af94e772ef7 #1 SMP PREEMPT_DYNAMIC Sun May 18 15:54:12 CST 2025
> MKFS_OPTIONS  -- /dev/sdb2
> MOUNT_OPTIONS -- /dev/sdb2 /fs/scratch
> 
> btrfs/220       [failed, exit status 1]- output mismatch (see /lkp/benchmarks/xfstests/results//btrfs/220.out.bad)
>      --- tests/btrfs/220.out	2025-05-26 16:25:04.000000000 +0000
>      +++ /lkp/benchmarks/xfstests/results//btrfs/220.out.bad	2025-06-01 10:11:04.131877139 +0000
>      @@ -1,2 +1,5 @@
>       QA output created by 220
>      -Silence is golden
>      +mount: /fs/scratch: wrong fs type, bad option, bad superblock on /dev/sdb2, missing codepage or helper program, or other error.
>      +       dmesg(1) may have more information after failed mount system call.
>      +mount -o nologreplay,ro /dev/sdb2 /fs/scratch failed
>      +(see /lkp/benchmarks/xfstests/results//btrfs/220.full for details)
>      ...
>      (Run 'diff -u /lkp/benchmarks/xfstests/tests/btrfs/220.out /lkp/benchmarks/xfstests/results//btrfs/220.out.bad'  to see the entire diff)
> Ran: btrfs/220
> Failures: btrfs/220
> Failed 1 of 1 tests
> 
> 
> 
> 
> The kernel config and materials to reproduce are available at:
> https://download.01.org/0day-ci/archive/20250604/202506042235.7e3a37da-lkp@intel.com
> 
> 
>