From: kernel test robot <oliver.sang@intel.com>
To: Ritesh Harjani <ritesh.list@gmail.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-ext4@vger.kernel.org>, <oliver.sang@intel.com>
Subject: [riteshharjani:ext2-iomap-lsfmm-rfcv2] [ext2] 44544ffe4d: xfstests.generic.093.fail
Date: Thu, 14 Mar 2024 12:57:07 +0800 [thread overview]
Message-ID: <202403141056.44846b46-oliver.sang@intel.com> (raw)
Hello,
kernel test robot noticed "xfstests.generic.093.fail" on:
commit: 44544ffe4db115b2fbd8d029ff447daea860c2d1 ("ext2: Convert ext2 regular file buffered I/O to use iomap")
https://github.com/riteshharjani/linux ext2-iomap-lsfmm-rfcv2
in testcase: xfstests
version: xfstests-x86_64-386c7b6a-1_20240304
with following parameters:
disk: 4HDD
fs: ext2
test: generic-093
compiler: gcc-12
test machine: 8 threads Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz (Skylake) with 28G 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/202403141056.44846b46-oliver.sang@intel.com
2024-03-09 17:31:14 export TEST_DIR=/fs/sdb1
2024-03-09 17:31:14 export TEST_DEV=/dev/sdb1
2024-03-09 17:31:14 export FSTYP=ext2
2024-03-09 17:31:15 export SCRATCH_MNT=/fs/scratch
2024-03-09 17:31:15 mkdir /fs/scratch -p
2024-03-09 17:31:15 export SCRATCH_DEV=/dev/sdb4
2024-03-09 17:31:15 echo generic/093
2024-03-09 17:31:15 ./check -E tests/exclude/ext2 generic/093
FSTYP -- ext2
PLATFORM -- Linux/x86_64 lkp-skl-d01 6.8.0-rc7-00022-g44544ffe4db1 #1 SMP PREEMPT_DYNAMIC Sat Mar 9 20:42:52 CST 2024
MKFS_OPTIONS -- -F /dev/sdb4
MOUNT_OPTIONS -- -o acl,user_xattr /dev/sdb4 /fs/scratch
generic/093 - output mismatch (see /lkp/benchmarks/xfstests/results//generic/093.out.bad)
--- tests/generic/093.out 2024-03-04 19:06:51.000000000 +0000
+++ /lkp/benchmarks/xfstests/results//generic/093.out.bad 2024-03-09 17:35:42.412272485 +0000
@@ -3,6 +3,7 @@
**** Verifying that appending to file clears capabilities ****
file cap_chown=ep
data1
+file cap_chown=ep
**** Verifying that appending to file doesn't clear other xattrs ****
data1
...
(Run 'diff -u /lkp/benchmarks/xfstests/tests/generic/093.out /lkp/benchmarks/xfstests/results//generic/093.out.bad' to see the entire diff)
Ran: generic/093
Failures: generic/093
Failed 1 of 1 tests
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20240314/202403141056.44846b46-oliver.sang@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-03-14 4:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202403141056.44846b46-oliver.sang@intel.com \
--to=oliver.sang@intel.com \
--cc=linux-ext4@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=ritesh.list@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).