linux-kernel - Re: [btrfs] 3ae92b3782: xfstests.generic.269.fail

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: <20190903132531.ojllcte3au7ipggd@MacBook-Pro-91.local>
Date:   Tue, 3 Sep 2019 09:25:32 -0400
From:   Josef Bacik <josef@...icpanda.com>
To:     kernel test robot <rong.a.chen@...el.com>
Cc:     Josef Bacik <josef@...icpanda.com>,
        David Sterba <dsterba@...e.com>,
        LKML <linux-kernel@...r.kernel.org>,
        Stephen Rothwell <sfr@...b.auug.org.au>, lkp@...org
Subject: Re: [btrfs]  3ae92b3782: xfstests.generic.269.fail

On Tue, Sep 03, 2019 at 04:06:33PM +0800, kernel test robot wrote:
> FYI, we noticed the following commit (built with gcc-7):
> 
> commit: 3ae92b3782182d282a92573abe95c96d34ca6e73 ("btrfs: change the minimum global reserve size")
> https://kernel.googlesource.com/pub/scm/linux/kernel/git/next/linux-next.git master
> 
> in testcase: xfstests
> with following parameters:
> 
> 	disk: 4HDD
> 	fs: btrfs
> 	test: generic-group13
> 
> 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: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 4G
> 
> caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
> 
> 

It would help if you could capture generic/269.full, but this is likely a
problem with fsck that I fixed a few weeks ago where we're seeing nbytes of an
inode is wrong, but there's an orphan item so it doesn't matter.  This patch
just made it more likely for us to have a still being iput'ed inode after a
transaction commit.  Thanks,

Josef