lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220323070834.GB16885@xsang-OptiPlex-9020>
Date:   Wed, 23 Mar 2022 15:08:34 +0800
From:   Oliver Sang <oliver.sang@...el.com>
To:     "Darrick J. Wong" <djwong@...nel.org>
Cc:     LKML <linux-kernel@...r.kernel.org>, lkp@...ts.01.org,
        lkp@...el.com, xfs <linux-xfs@...r.kernel.org>,
        fstests <fstests@...r.kernel.org>
Subject: Re: [xfs]  1fc3f2c3c9: xfstests.xfs.529.fail

hi, Darrick,

On Tue, Mar 22, 2022 at 09:27:33AM -0700, Darrick J. Wong wrote:
> On Tue, Mar 22, 2022 at 09:54:02PM +0800, kernel test robot wrote:
> > 
> > 
> > Greeting,
> > 
> > FYI, we noticed the following commit (built with gcc-9):
> > 
> > commit: 1fc3f2c3c928c88654d4716af5cc4dee07b3a1c4 ("xfs: only free posteof blocks on first close")
> > https://git.kernel.org/cgit/linux/kernel/git/djwong/xfs-linux.git vectorized-scrub
> > 
> > in testcase: xfstests
> > version: xfstests-x86_64-1de1db8-1_20220217
> > with following parameters:
> > 
> > 	disk: 4HDD
> > 	fs: xfs
> > 	test: xfs-group-52
> > 	ucode: 0x21
> > 
> > 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 with 8G memory
> > 
> > caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
> > 
> > 
> > If you fix the issue, kindly add following tag
> > Reported-by: kernel test robot <oliver.sang@...el.com>
> > 
> 
> Could you export DIFF_LENGTH=0 in the test environment so that we get
> the full diff here, please?

the full diff is as below (also attached dmesg, full log, log for 529 in case
helpful):

xfs/529 [failed, exit status 1]- output mismatch (see /lkp/benchmarks/xfstests/results//xfs/529.out.bad)
    --- tests/xfs/529.out       2022-02-17 11:55:00.000000000 +0000
    +++ /lkp/benchmarks/xfstests/results//xfs/529.out.bad       2022-03-23 06:18:39.815036267 +0000
    @@ -4,21 +4,4 @@
     Inject reduce_max_iextents error tag
     Create fragmented file
     Verify $testfile's extent count
    -Disable reduce_max_iextents error tag
    -* Fallocate unwritten extents
    -Inject reduce_max_iextents error tag
    -Fallocate fragmented file
    -Verify $testfile's extent count
    -Disable reduce_max_iextents error tag
    -* Directio write
    -Inject reduce_max_iextents error tag
    -Create fragmented file via directio writes
    -Verify $testfile's extent count
    -Disable reduce_max_iextents error tag
    -* Extend quota inodes
    -Consume free space
    -Create fragmented filesystem
    -Inject reduce_max_iextents error tag
    -Inject bmap_alloc_minlen_extent error tag
    -Extend uquota file
    -Verify uquota inode's extent count
    +Extent count overflow check failed: nextents = 15


> 
> --D
> 

Download attachment "dmesg.xz" of type "application/x-xz" (6184 bytes)

View attachment "xfstests" of type "text/plain" (2463 bytes)

View attachment "529.full" of type "text/plain" (1633 bytes)

View attachment "529.out.bad" of type "text/plain" (228 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ