From: kernel test robot <oliver.sang@intel.com>
To: David Howells <dhowells@redhat.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-kernel@vger.kernel.org>,
Christian Brauner <brauner@kernel.org>,
Jeff Layton <jlayton@kernel.org>,
Steve French <stfrench@microsoft.com>,
Enzo Matsumiya <ematsumiya@suse.de>, <netfs@lists.linux.dev>,
<linux-fsdevel@vger.kernel.org>, <oliver.sang@intel.com>
Subject: [linus:master] [netfs] 9b038d004c: xfstests.generic.617.fail
Date: Tue, 11 Jun 2024 15:59:49 +0800 [thread overview]
Message-ID: <202406111527.994f629c-oliver.sang@intel.com> (raw)
Hello,
kernel test robot noticed "xfstests.generic.617.fail" on:
commit: 9b038d004ce95551cb35381c49fe896c5bc11ffe ("netfs: Fix io_uring based write-through")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
[test failed on linus/master 2df0193e62cf887f373995fb8a91068562784adc]
[test failed on linux-next/master ee78a17615ad0cfdbbc27182b1047cd36c9d4d5f]
in testcase: xfstests
version: xfstests-x86_64-98379713-1_20240603
with following parameters:
disk: 4HDD
fs: ext4
fs2: smbv3
test: generic-617
compiler: gcc-13
test machine: 4 threads Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz (Skylake) with 32G 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/202406111527.994f629c-oliver.sang@intel.com
2024-06-06 01:33:53 mount /dev/sda1 /fs/sda1
2024-06-06 01:33:54 mkdir -p /smbv3//cifs/sda1
2024-06-06 01:33:54 export FSTYP=cifs
2024-06-06 01:33:54 export TEST_DEV=//localhost/fs/sda1
2024-06-06 01:33:54 export TEST_DIR=/smbv3//cifs/sda1
2024-06-06 01:33:54 export CIFS_MOUNT_OPTIONS=-ousername=root,password=pass,noperm,vers=3.0,mfsymlinks,actimeo=0
2024-06-06 01:33:54 echo generic/617
2024-06-06 01:33:54 ./check -E tests/cifs/exclude.incompatible-smb3.txt -E tests/cifs/exclude.very-slow.txt generic/617
FSTYP -- cifs
PLATFORM -- Linux/x86_64 lkp-skl-d05 6.9.0-10324-g9b038d004ce9 #1 SMP PREEMPT_DYNAMIC Thu Jun 6 03:01:37 CST 2024
generic/617 - output mismatch (see /lkp/benchmarks/xfstests/results//generic/617.out.bad)
--- tests/generic/617.out 2024-06-03 12:10:00.000000000 +0000
+++ /lkp/benchmarks/xfstests/results//generic/617.out.bad 2024-06-06 01:34:51.537054472 +0000
@@ -1,2 +1,12 @@
QA output created by 617
+uring write bad io length: 0 instead of 110592
+short write: 0x0 bytes instead of 0x1b000
+LOG DUMP (4 total operations):
+1( 1 mod 256): SKIPPED (no operation)
+2( 2 mod 256): SKIPPED (no operation)
+3( 3 mod 256): SKIPPED (no operation)
...
(Run 'diff -u /lkp/benchmarks/xfstests/tests/generic/617.out /lkp/benchmarks/xfstests/results//generic/617.out.bad' to see the entire diff)
Ran: generic/617
Failures: generic/617
Failed 1 of 1 tests
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20240611/202406111527.994f629c-oliver.sang@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-06-11 8:00 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=202406111527.994f629c-oliver.sang@intel.com \
--to=oliver.sang@intel.com \
--cc=brauner@kernel.org \
--cc=dhowells@redhat.com \
--cc=ematsumiya@suse.de \
--cc=jlayton@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=netfs@lists.linux.dev \
--cc=oe-lkp@lists.linux.dev \
--cc=stfrench@microsoft.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 NNTP newsgroup(s).