From: kernel test robot <oliver.sang@intel.com>
To: Wengang Wang <wen.gang.wang@oracle.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-xfs@vger.kernel.org>, <david@fromorbit.com>,
<wen.gang.wang@oracle.com>, <oliver.sang@intel.com>
Subject: Re: [PATCH] xfs: allow changing extsize on file
Date: Mon, 20 May 2024 12:58:39 +0800 [thread overview]
Message-ID: <202405201028.ca3b53bf-oliver.sang@intel.com> (raw)
In-Reply-To: <20240508170343.2774-1-wen.gang.wang@oracle.com>
hi, Wengang Wang,
we noticed "this is more a question than a patch."
but not sure if below report could supply any useful information to you, so
still send FYI what we observed in our tests.
Hello,
kernel test robot noticed "xfstests.xfs.207.fail" on:
commit: ab25dcd364e632586fe0bd3a2cdb194e03f5b484 ("[PATCH] xfs: allow changing extsize on file")
url: https://github.com/intel-lab-lkp/linux/commits/Wengang-Wang/xfs-allow-changing-extsize-on-file/20240509-010818
base: https://git.kernel.org/cgit/fs/xfs/xfs-linux.git for-next
patch link: https://lore.kernel.org/all/20240508170343.2774-1-wen.gang.wang@oracle.com/
patch subject: [PATCH] xfs: allow changing extsize on file
in testcase: xfstests
version: xfstests-x86_64-b26d68da-1_20240517
with following parameters:
disk: 4HDD
fs: xfs
test: xfs-207
compiler: gcc-13
test machine: 4 threads Intel(R) Xeon(R) CPU E3-1225 v5 @ 3.30GHz (Skylake) with 16G 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/202405201028.ca3b53bf-oliver.sang@intel.com
2024-05-17 16:19:24 export TEST_DIR=/fs/sda1
2024-05-17 16:19:24 export TEST_DEV=/dev/sda1
2024-05-17 16:19:24 export FSTYP=xfs
2024-05-17 16:19:24 export SCRATCH_MNT=/fs/scratch
2024-05-17 16:19:24 mkdir /fs/scratch -p
2024-05-17 16:19:24 export SCRATCH_DEV=/dev/sda4
2024-05-17 16:19:24 export SCRATCH_LOGDEV=/dev/sda2
2024-05-17 16:19:24 export SCRATCH_XFS_LIST_METADATA_FIELDS=u3.sfdir3.hdr.parent.i4
2024-05-17 16:19:24 export SCRATCH_XFS_LIST_FUZZ_VERBS=random
2024-05-17 16:19:24 export MKFS_OPTIONS=-mreflink=1
2024-05-17 16:19:24 echo xfs/207
2024-05-17 16:19:24 ./check xfs/207
FSTYP -- xfs (debug)
PLATFORM -- Linux/x86_64 lkp-skl-d06 6.9.0-rc4-00248-gab25dcd364e6 #1 SMP PREEMPT_DYNAMIC Fri May 17 14:27:24 CST 2024
MKFS_OPTIONS -- -f -mreflink=1 /dev/sda4
MOUNT_OPTIONS -- /dev/sda4 /fs/scratch
xfs/207 - output mismatch (see /lkp/benchmarks/xfstests/results//xfs/207.out.bad)
--- tests/xfs/207.out 2024-05-17 14:38:40.000000000 +0000
+++ /lkp/benchmarks/xfstests/results//xfs/207.out.bad 2024-05-17 16:20:09.902112701 +0000
@@ -3,12 +3,11 @@
Create the original files
Set extsz and cowextsz on zero byte file
Set extsz and cowextsz on 1Mbyte file
-xfs_io: FS_IOC_FSSETXATTR SCRATCH_MNT/test-207/file2: Invalid argument
Check extsz and cowextsz settings on zero byte file
[1048576] SCRATCH_MNT/test-207/file1
[1048576] SCRATCH_MNT/test-207/file1
...
(Run 'diff -u /lkp/benchmarks/xfstests/tests/xfs/207.out /lkp/benchmarks/xfstests/results//xfs/207.out.bad' to see the entire diff)
Ran: xfs/207
Failures: xfs/207
Failed 1 of 1 tests
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20240520/202405201028.ca3b53bf-oliver.sang@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2024-05-20 4:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-08 17:03 [PATCH] xfs: allow changing extsize on file Wengang Wang
2024-05-11 1:56 ` Dave Chinner
2024-05-13 17:17 ` Wengang Wang
2024-05-20 4:58 ` kernel test robot [this message]
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=202405201028.ca3b53bf-oliver.sang@intel.com \
--to=oliver.sang@intel.com \
--cc=david@fromorbit.com \
--cc=linux-xfs@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=wen.gang.wang@oracle.com \
/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