* [kdave-btrfs-devel:dev/guilherme/temp-fsid-v4] [btrfs] 479361d32b: xfstests.btrfs.185.fail
@ 2023-10-31 7:46 kernel test robot
2023-10-31 9:23 ` Anand Jain
0 siblings, 1 reply; 3+ messages in thread
From: kernel test robot @ 2023-10-31 7:46 UTC (permalink / raw)
To: Anand Jain; +Cc: oe-lkp, lkp, David Sterba, linux-btrfs, oliver.sang
Hello,
kernel test robot noticed "xfstests.btrfs.185.fail" on:
commit: 479361d32be2d93c5fe727cc5cd2ea2c187635a8 ("btrfs: scan but don't register device on single device filesystem")
https://github.com/kdave/btrfs-devel.git dev/guilherme/temp-fsid-v4
in testcase: xfstests
version: xfstests-x86_64-b15b6cc-1_20230925
with following parameters:
disk: 6HDD
fs: btrfs
test: btrfs-185
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@intel.com>
| Closes: https://lore.kernel.org/oe-lkp/202310311425.c2e34aef-oliver.sang@intel.com
btrfs/185 [failed, exit status 1]- output mismatch (see /lkp/benchmarks/xfstests/results//btrfs/185.out.bad)
--- tests/btrfs/185.out 2023-09-25 16:30:56.000000000 +0000
+++ /lkp/benchmarks/xfstests/results//btrfs/185.out.bad 2023-09-27 11:53:55.152939282 +0000
@@ -1,2 +1,3 @@
QA output created by 185
-Silence is golden
+cloned device scan should fail
+(see /lkp/benchmarks/xfstests/results//btrfs/185.full for details)
...
(Run 'diff -u /lkp/benchmarks/xfstests/tests/btrfs/185.out /lkp/benchmarks/xfstests/results//btrfs/185.out.bad' to see the entire diff)
HINT: You _MAY_ be missing kernel fix:
a9261d4125c9 btrfs: harden agaist duplicate fsid on scanned devices
Ran: btrfs/185
Failures: btrfs/185
Failed 1 of 1 tests
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20231031/202310311425.c2e34aef-oliver.sang@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [kdave-btrfs-devel:dev/guilherme/temp-fsid-v4] [btrfs] 479361d32b: xfstests.btrfs.185.fail
2023-10-31 7:46 [kdave-btrfs-devel:dev/guilherme/temp-fsid-v4] [btrfs] 479361d32b: xfstests.btrfs.185.fail kernel test robot
@ 2023-10-31 9:23 ` Anand Jain
2023-10-31 11:22 ` David Sterba
0 siblings, 1 reply; 3+ messages in thread
From: Anand Jain @ 2023-10-31 9:23 UTC (permalink / raw)
To: kernel test robot; +Cc: oe-lkp, lkp, David Sterba, linux-btrfs
Thanks for the report.
> +cloned device scan should fail
Your fstests is missing the following commit:
1348ed0e256a ("fstests: btrfs/185 update for single device pseudo
device-scan")
Pls upgrade.
Thanks, Anand
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [kdave-btrfs-devel:dev/guilherme/temp-fsid-v4] [btrfs] 479361d32b: xfstests.btrfs.185.fail
2023-10-31 9:23 ` Anand Jain
@ 2023-10-31 11:22 ` David Sterba
0 siblings, 0 replies; 3+ messages in thread
From: David Sterba @ 2023-10-31 11:22 UTC (permalink / raw)
To: Anand Jain; +Cc: kernel test robot, oe-lkp, lkp, David Sterba, linux-btrfs
On Tue, Oct 31, 2023 at 05:23:18PM +0800, Anand Jain wrote:
> Thanks for the report.
>
> > +cloned device scan should fail
>
> Your fstests is missing the following commit:
> 1348ed0e256a ("fstests: btrfs/185 update for single device pseudo
> device-scan")
> Pls upgrade.
Yes for the fstests upgrade, but the tested branch is some old snapshot
of the temp_fsid feature, I don't even have the branch anywhere.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2023-10-31 11:29 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-10-31 7:46 [kdave-btrfs-devel:dev/guilherme/temp-fsid-v4] [btrfs] 479361d32b: xfstests.btrfs.185.fail kernel test robot
2023-10-31 9:23 ` Anand Jain
2023-10-31 11:22 ` David Sterba
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox