From: kernel test robot <oliver.sang@intel.com>
To: Anand Jain <anand.jain@oracle.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
David Sterba <dsterba@suse.com>, <linux-btrfs@vger.kernel.org>,
<oliver.sang@intel.com>
Subject: [kdave-btrfs-devel:dev/guilherme/temp-fsid-v4] [btrfs] 479361d32b: xfstests.btrfs.185.fail
Date: Tue, 31 Oct 2023 15:46:23 +0800 [thread overview]
Message-ID: <202310311425.c2e34aef-oliver.sang@intel.com> (raw)
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
next reply other threads:[~2023-10-31 7:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 7:46 kernel test robot [this message]
2023-10-31 9:23 ` [kdave-btrfs-devel:dev/guilherme/temp-fsid-v4] [btrfs] 479361d32b: xfstests.btrfs.185.fail Anand Jain
2023-10-31 11:22 ` David Sterba
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=202310311425.c2e34aef-oliver.sang@intel.com \
--to=oliver.sang@intel.com \
--cc=anand.jain@oracle.com \
--cc=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.