From: kernel test robot <oliver.sang@intel.com>
To: Anand Jain <anand.jain@oracle.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
Linux Memory Management List <linux-mm@kvack.org>,
David Sterba <dsterba@suse.com>,
"Guilherme G. Piccoli" <gpiccoli@igalia.com>,
<linux-btrfs@vger.kernel.org>, <oliver.sang@intel.com>
Subject: [linux-next:master] [btrfs] a5b8a5f9f8: xfstests.btrfs.219.fail
Date: Wed, 25 Oct 2023 16:55:35 +0800 [thread overview]
Message-ID: <202310251645.5fe5495a-oliver.sang@intel.com> (raw)
Hello,
kernel test robot noticed "xfstests.btrfs.219.fail" on:
commit: a5b8a5f9f8355d27a4f8d0afa93427f16d2f3c1e ("btrfs: support cloned-device mount capability")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
[test failed on linux-next/master 2030579113a1b1b5bfd7ff24c0852847836d8fd1]
in testcase: xfstests
version: xfstests-x86_64-4d811ae-1_20231009
with following parameters:
disk: 6HDD
fs: btrfs
test: btrfs-219
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/202310251645.5fe5495a-oliver.sang@intel.com
2023-10-21 19:53:10 export TEST_DIR=/fs/sda1
2023-10-21 19:53:10 export TEST_DEV=/dev/sda1
2023-10-21 19:53:10 export FSTYP=btrfs
2023-10-21 19:53:10 export SCRATCH_MNT=/fs/scratch
2023-10-21 19:53:10 mkdir /fs/scratch -p
2023-10-21 19:53:10 export SCRATCH_DEV_POOL="/dev/sda2 /dev/sda3 /dev/sda4 /dev/sda5 /dev/sda6"
2023-10-21 19:53:10 echo btrfs/219
2023-10-21 19:53:10 ./check btrfs/219
FSTYP -- btrfs
PLATFORM -- Linux/x86_64 lkp-hsw-d01 6.6.0-rc5-00214-ga5b8a5f9f835 #1 SMP PREEMPT_DYNAMIC Sun Oct 22 03:34:58 CST 2023
MKFS_OPTIONS -- /dev/sda2
MOUNT_OPTIONS -- /dev/sda2 /fs/scratch
btrfs/219 [failed, exit status 1]- output mismatch (see /lkp/benchmarks/xfstests/results//btrfs/219.out.bad)
--- tests/btrfs/219.out 2023-10-09 16:50:26.000000000 +0000
+++ /lkp/benchmarks/xfstests/results//btrfs/219.out.bad 2023-10-21 19:53:35.090528975 +0000
@@ -1,2 +1,4 @@
QA output created by 219
-Silence is golden
+We were allowed to mount when we should have failed
+(see /lkp/benchmarks/xfstests/results//btrfs/219.full for details)
+rm: cannot remove '/fs/sda1/219.mnt1': Device or resource busy
...
(Run 'diff -u /lkp/benchmarks/xfstests/tests/btrfs/219.out /lkp/benchmarks/xfstests/results//btrfs/219.out.bad' to see the entire diff)
HINT: You _MAY_ be missing kernel fix:
5f58d783fd78 btrfs: free device in btrfs_close_devices for a single device filesystem
Ran: btrfs/219
Failures: btrfs/219
Failed 1 of 1 tests
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20231025/202310251645.5fe5495a-oliver.sang@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2023-10-25 8:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-25 8:55 kernel test robot [this message]
2023-10-25 10:53 ` Anand Jain
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=202310251645.5fe5495a-oliver.sang@intel.com \
--to=oliver.sang@intel.com \
--cc=anand.jain@oracle.com \
--cc=dsterba@suse.com \
--cc=gpiccoli@igalia.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox