[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <d288921c-af80-0623-60eb-ff8c24d92985@intel.com>
Date: Wed, 4 Sep 2019 08:54:10 +0800
From: Rong Chen <rong.a.chen@...el.com>
To: Josef Bacik <josef@...icpanda.com>
Cc: 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 9/3/19 9:25 PM, Josef Bacik wrote:
> 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
Hi Josef,
I enclose the generic/269.full file for your reference.
Best Regards,
Rong Chen
View attachment "269.full" of type "text/plain" (4551 bytes)
Powered by blists - more mailing lists