All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <oliver.sang@intel.com>
To: Jan Kara <jack@suse.cz>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
	<linux-kernel@vger.kernel.org>, <linux-ext4@vger.kernel.org>,
	<oliver.sang@intel.com>
Subject: [linus:master] [ext2]  bc943f4872: xfstests.generic.269.fail
Date: Tue, 21 Nov 2023 22:11:49 +0800	[thread overview]
Message-ID: <202311211653.3a9e8678-oliver.sang@intel.com> (raw)



Hello,

kernel test robot noticed "xfstests.generic.269.fail" on:

commit: bc943f4872a722c5cc64d1cf41daaaf4ec63158e ("ext2: Don't flush page immediately for DIRSYNC directories")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master

[test failed on linus/master 791c8ab095f71327899023223940dd52257a4173]
[test failed on linux-next/master eff99d8edbed7918317331ebd1e365d8e955d65e]

in testcase: xfstests
version: xfstests-x86_64-d860afa-1_20231030
with following parameters:

	disk: 4HDD
	fs: ext2
	test: generic-269



compiler: gcc-12
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/202311211653.3a9e8678-oliver.sang@intel.com

2023-11-18 01:55:44 export TEST_DIR=/fs/sda1
2023-11-18 01:55:44 export TEST_DEV=/dev/sda1
2023-11-18 01:55:44 export FSTYP=ext2
2023-11-18 01:55:44 export SCRATCH_MNT=/fs/scratch
2023-11-18 01:55:44 mkdir /fs/scratch -p
2023-11-18 01:55:44 export SCRATCH_DEV=/dev/sda4
2023-11-18 01:55:44 echo generic/269
2023-11-18 01:55:44 ./check -E tests/exclude/ext2 generic/269
FSTYP         -- ext2
PLATFORM      -- Linux/x86_64 lkp-skl-d02 6.1.0-rc2-00005-gbc943f4872a7 #1 SMP PREEMPT_DYNAMIC Sat Nov 18 03:54:42 CST 2023
MKFS_OPTIONS  -- -F /dev/sda4
MOUNT_OPTIONS -- -o acl,user_xattr /dev/sda4 /fs/scratch

generic/269       - output mismatch (see /lkp/benchmarks/xfstests/results//generic/269.out.bad)
    --- tests/generic/269.out	2023-10-30 17:13:51.000000000 +0000
    +++ /lkp/benchmarks/xfstests/results//generic/269.out.bad	2023-11-18 02:03:10.606457744 +0000
    @@ -3,3 +3,57 @@
     Run fsstress
     
     Run dd writers in parallel
    +p4a: No such file or directory
    +p4b: No such file or directory
    +p4c: No such file or directory
    +p4d: No such file or directory
    ...
    (Run 'diff -u /lkp/benchmarks/xfstests/tests/generic/269.out /lkp/benchmarks/xfstests/results//generic/269.out.bad'  to see the entire diff)
Ran: generic/269
Failures: generic/269
Failed 1 of 1 tests




The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20231121/202311211653.3a9e8678-oliver.sang@intel.com



-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


             reply	other threads:[~2023-11-21 14:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-21 14:11 kernel test robot [this message]
2023-11-21 18:28 ` [linus:master] [ext2] bc943f4872: xfstests.generic.269.fail Ritesh Harjani
2023-11-22  3:03   ` Oliver Sang

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=202311211653.3a9e8678-oliver.sang@intel.com \
    --to=oliver.sang@intel.com \
    --cc=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.