From: kernel test robot <oliver.sang@intel.com>
To: David Howells <dhowells@redhat.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
Jeff Layton <jlayton@kernel.org>, <v9fs@lists.linux.dev>,
<linux-afs@lists.infradead.org>, <ceph-devel@vger.kernel.org>,
<netfs@lists.linux.dev>, <linux-fsdevel@vger.kernel.org>,
<linux-nfs@vger.kernel.org>, <linux-cifs@vger.kernel.org>,
<samba-technical@lists.samba.org>, <oliver.sang@intel.com>
Subject: [dhowells-fs:netfs-writeback] [netfs] 383151c58c: xfstests.generic.465.fail
Date: Thu, 8 Aug 2024 16:51:46 +0800 [thread overview]
Message-ID: <202408081612.9d5c488b-oliver.sang@intel.com> (raw)
Hello,
kernel test robot noticed "xfstests.generic.465.fail" on:
commit: 383151c58c85c735c45970bf3cde7f6fc96f958d ("netfs: Speed up buffered reading")
https://git.kernel.org/cgit/linux/kernel/git/dhowells/linux-fs.git netfs-writeback
in testcase: xfstests
version: xfstests-x86_64-b3b32377-1_20240729
with following parameters:
disk: 4HDD
fs: ext4
fs2: smbv2
test: generic-465
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/202408081612.9d5c488b-oliver.sang@intel.com
2024-08-02 13:50:42 mount /dev/sda1 /fs/sda1
2024-08-02 13:50:43 mkdir -p /smbv2//cifs/sda1
2024-08-02 13:50:43 export FSTYP=cifs
2024-08-02 13:50:43 export TEST_DEV=//localhost/fs/sda1
2024-08-02 13:50:43 export TEST_DIR=/smbv2//cifs/sda1
2024-08-02 13:50:43 export CIFS_MOUNT_OPTIONS=-ousername=root,password=pass,noperm,vers=2.0,mfsymlinks,actimeo=0
2024-08-02 13:50:43 echo generic/465
2024-08-02 13:50:43 ./check -E tests/cifs/exclude.incompatible-smb2.txt -E tests/cifs/exclude.very-slow.txt generic/465
FSTYP -- cifs
PLATFORM -- Linux/x86_64 lkp-skl-d05 6.11.0-rc1-00022-g383151c58c85 #1 SMP PREEMPT_DYNAMIC Fri Aug 2 18:33:48 CST 2024
generic/465 - output mismatch (see /lkp/benchmarks/xfstests/results//generic/465.out.bad)
--- tests/generic/465.out 2024-07-29 17:28:39.000000000 +0000
+++ /lkp/benchmarks/xfstests/results//generic/465.out.bad 2024-08-02 13:51:40.918295861 +0000
@@ -1,3 +1,260 @@
QA output created by 465
non-aio dio test
+read file: No data available
+read file: No data available
+read file: No data available
+read file: No data available
+read file: No data available
...
(Run 'diff -u /lkp/benchmarks/xfstests/tests/generic/465.out /lkp/benchmarks/xfstests/results//generic/465.out.bad' to see the entire diff)
Ran: generic/465
Failures: generic/465
Failed 1 of 1 tests
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20240808/202408081612.9d5c488b-oliver.sang@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-08-08 8:52 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=202408081612.9d5c488b-oliver.sang@intel.com \
--to=oliver.sang@intel.com \
--cc=ceph-devel@vger.kernel.org \
--cc=dhowells@redhat.com \
--cc=jlayton@kernel.org \
--cc=linux-afs@lists.infradead.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=lkp@intel.com \
--cc=netfs@lists.linux.dev \
--cc=oe-lkp@lists.linux.dev \
--cc=samba-technical@lists.samba.org \
--cc=v9fs@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