From: Oliver Sang <oliver.sang@intel.com>
To: Dave Chinner <david@fromorbit.com>
Cc: Guo Xuenan <guoxuenan@huawei.com>, <lkp@lists.01.org>,
<lkp@intel.com>, Hou Tao <houtao1@huawei.com>,
<linux-xfs@vger.kernel.org>
Subject: Re: [xfs] a1df10d42b: xfstests.generic.31*.fail
Date: Sun, 9 Oct 2022 15:17:55 +0800 [thread overview]
Message-ID: <Y0J1oxBFwW53udvJ@xsang-OptiPlex-9020> (raw)
In-Reply-To: <20221005213543.GP3600936@dread.disaster.area>
[-- Attachment #1: Type: text/plain, Size: 2054 bytes --]
Hi Dave,
On Thu, Oct 06, 2022 at 08:35:43AM +1100, Dave Chinner wrote:
> On Wed, Oct 05, 2022 at 09:45:12PM +0800, kernel test robot wrote:
> >
> > Greeting,
> >
> > FYI, we noticed the following commit (built with gcc-11):
> >
> > commit: a1df10d42ba99c946f6a574d4d31951bc0a57e33 ("xfs: fix exception caused by unexpected illegal bestcount in leaf dir")
> > url: https://github.com/intel-lab-lkp/linux/commits/UPDATE-20220929-162751/Guo-Xuenan/xfs-fix-uaf-when-leaf-dir-bestcount-not-match-with-dir-data-blocks/20220831-195920
> >
> > in testcase: xfstests
> > version: xfstests-x86_64-5a5e419-1_20220927
> > with following parameters:
> >
> > disk: 4HDD
> > fs: xfs
> > test: generic-group-15
> >
> > test-description: xfstests is a regression test suite for xfs and other files ystems.
> > test-url: git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git
> >
> >
> > on test machine: 4 threads 1 sockets Intel(R) Core(TM) i3-3220 CPU @ 3.30GHz (Ivy Bridge) with 8G memory
> >
> > caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
>
> THe attached dmesg ends at:
>
> [...]
> [ 102.727610][ T315] generic/309 IPMI BMC is not supported on this machine, skip bmc-watchdog setup!
> [ 102.727630][ T315]
> [ 103.884498][ T7407] XFS (sda1): EXPERIMENTAL online scrub feature in use. Use at your own risk!
> [ 103.993962][ T7431] XFS (sda1): Unmounting Filesystem
> [ 104.193659][ T7580] XFS (sda1): Mounting V5 Filesystem
> [ 104.221178][ T7580] XFS (sda1): Ending clean mount
> [ 104.223821][ T7580] xfs filesystem being mounted at /fs/sda1 supports timestamps until 2038 (0x7fffffff)
> [ 104.285615][ T315] 2s
> [ 104.285629][ T315]
> [ 104.339232][ T1469] run fstests generic/310 at 2022-10-01 13:36:36
> (END)
>
> The start of the failed test. Do you have the logs from generic/310
> so we might have some idea what corruption/shutdown event occurred
> during that test run?
sorry for that. I attached dmesg for another run.
>
> -Dave.
> --
> Dave Chinner
> david@fromorbit.com
[-- Attachment #2: dmesg.xz --]
[-- Type: application/x-xz, Size: 9036 bytes --]
next prev parent reply other threads:[~2022-10-09 7:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-05 13:45 [xfs] a1df10d42b: xfstests.generic.31*.fail kernel test robot
2022-10-05 21:35 ` Dave Chinner
2022-10-09 7:17 ` Oliver Sang [this message]
2022-10-10 0:07 ` Dave Chinner
2022-10-10 0:32 ` [LKP] " Philip Li
2022-10-10 20:54 ` Dave Chinner
2022-10-11 1:25 ` Philip Li
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=Y0J1oxBFwW53udvJ@xsang-OptiPlex-9020 \
--to=oliver.sang@intel.com \
--cc=david@fromorbit.com \
--cc=guoxuenan@huawei.com \
--cc=houtao1@huawei.com \
--cc=linux-xfs@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
/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).