From: "Darrick J. Wong" <djwong@kernel.org>
To: kernel test robot <oliver.sang@intel.com>
Cc: oe-lkp@lists.linux.dev, lkp@intel.com,
linux-kernel@vger.kernel.org,
Chandan Babu R <chandanbabu@kernel.org>,
Christoph Hellwig <hch@lst.de>,
linux-xfs@vger.kernel.org
Subject: Re: [linus:master] [xfs] 38de567906: xfstests.xfs.348.fail
Date: Mon, 17 Jun 2024 17:55:00 -0700 [thread overview]
Message-ID: <20240618005500.GC103057@frogsfrogsfrogs> (raw)
In-Reply-To: <202406171629.fa23d1c3-oliver.sang@intel.com>
On Mon, Jun 17, 2024 at 04:49:07PM +0800, kernel test robot wrote:
>
>
> Hello,
>
> kernel test robot noticed "xfstests.xfs.348.fail" on:
>
> commit: 38de567906d95c397d87f292b892686b7ec6fbc3 ("xfs: allow symlinks with short remote targets")
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
Known bug in fstests, will send patch asap...
--D
> [test failed on linus/master 8a92980606e3585d72d510a03b59906e96755b8a]
> [test failed on linux-next/master d35b2284e966c0bef3e2182a5c5ea02177dd32e4]
>
> in testcase: xfstests
> version: xfstests-x86_64-98379713-1_20240603
> with following parameters:
>
> disk: 4HDD
> fs: xfs
> test: xfs-348
>
>
>
> 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/202406171629.fa23d1c3-oliver.sang@intel.com
>
>
>
> The kernel config and materials to reproduce are available at:
> https://download.01.org/0day-ci/archive/20240617/202406171629.fa23d1c3-oliver.sang@intel.com
>
>
> 2024-06-07 08:32:34 export TEST_DIR=/fs/sda1
> 2024-06-07 08:32:34 export TEST_DEV=/dev/sda1
> 2024-06-07 08:32:34 export FSTYP=xfs
> 2024-06-07 08:32:34 export SCRATCH_MNT=/fs/scratch
> 2024-06-07 08:32:34 mkdir /fs/scratch -p
> 2024-06-07 08:32:34 export SCRATCH_DEV=/dev/sda4
> 2024-06-07 08:32:34 export SCRATCH_LOGDEV=/dev/sda2
> 2024-06-07 08:32:34 export SCRATCH_XFS_LIST_METADATA_FIELDS=u3.sfdir3.hdr.parent.i4
> 2024-06-07 08:32:34 export SCRATCH_XFS_LIST_FUZZ_VERBS=random
> 2024-06-07 08:32:34 echo xfs/348
> 2024-06-07 08:32:34 ./check xfs/348
> FSTYP -- xfs (debug)
> PLATFORM -- Linux/x86_64 lkp-skl-d06 6.10.0-rc1-00005-g38de567906d9 #1 SMP PREEMPT_DYNAMIC Fri Jun 7 04:48:02 CST 2024
> MKFS_OPTIONS -- -f /dev/sda4
> MOUNT_OPTIONS -- /dev/sda4 /fs/scratch
>
> xfs/348 - output mismatch (see /lkp/benchmarks/xfstests/results//xfs/348.out.bad)
> --- tests/xfs/348.out 2024-06-03 12:10:00.000000000 +0000
> +++ /lkp/benchmarks/xfstests/results//xfs/348.out.bad 2024-06-07 08:33:19.134137710 +0000
> @@ -240,7 +240,7 @@
> would have junked entry "EMPTY" in directory PARENT_INO
> would have junked entry "FIFO" in directory PARENT_INO
> stat: cannot statx 'SCRATCH_MNT/test/DIR': Structure needs cleaning
> -stat: cannot statx 'SCRATCH_MNT/test/DATA': Structure needs cleaning
> +stat: 'SCRATCH_MNT/test/DATA' is a symbolic link
> stat: cannot statx 'SCRATCH_MNT/test/EMPTY': Structure needs cleaning
> stat: 'SCRATCH_MNT/test/SYMLINK' is a symbolic link
> ...
> (Run 'diff -u /lkp/benchmarks/xfstests/tests/xfs/348.out /lkp/benchmarks/xfstests/results//xfs/348.out.bad' to see the entire diff)
> Ran: xfs/348
> Failures: xfs/348
> Failed 1 of 1 tests
>
> --
> 0-DAY CI Kernel Test Service
> https://github.com/intel/lkp-tests/wiki
>
prev parent reply other threads:[~2024-06-18 0:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-17 8:49 [linus:master] [xfs] 38de567906: xfstests.xfs.348.fail kernel test robot
2024-06-18 0:55 ` Darrick J. Wong [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=20240618005500.GC103057@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=chandanbabu@kernel.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.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