From: Matthew Wilcox <willy@infradead.org>
To: kernel test robot <oliver.sang@intel.com>
Cc: David Sterba <dsterba@suse.com>, 0day robot <lkp@intel.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-btrfs@vger.kernel.org, lkp@lists.01.org
Subject: Re: [btrfs] 66a7a2412f: xfstests.btrfs.131.fail
Date: Thu, 16 Jun 2022 22:17:11 +0100 [thread overview]
Message-ID: <Yqud1/SooVDamiuP@casper.infradead.org> (raw)
In-Reply-To: <20220616143710.GF25633@xsang-OptiPlex-9020>
On Thu, Jun 16, 2022 at 10:37:10PM +0800, kernel test robot wrote:
> btrfs/131 - output mismatch (see /lkp/benchmarks/xfstests/results//btrfs/131.out.bad)
> --- tests/btrfs/131.out 2022-06-13 17:10:24.000000000 +0000
> +++ /lkp/benchmarks/xfstests/results//btrfs/131.out.bad 2022-06-15 18:54:06.505508542 +0000
> @@ -2,9 +2,9 @@
> Using free space cache
> free space tree is disabled
> Enabling free space tree
> -free space tree is enabled
> +free space tree is disabled
I think I know what's going on here:
compat_ro="$($BTRFS_UTIL_PROG inspect-internal dump-super "$SCRATCH_DEV"
| \
sed -rn 's/^compat_ro_flags\s+(.*)$/\1/p')"
if ((compat_ro & 0x1)); then
echo "free space tree is enabled"
else
echo "free space tree is disabled"
fi
dump-super is reading the super block out of the page cache, but this
change makes the page cache incoherent with what's on disc. We could
fix that by invalidating the page out of the page cache, but it may be
easier to just dump this patch and fix how we use the page cache to
write back the superblocks?
next prev parent reply other threads:[~2022-06-16 21:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 15:42 [PATCH] btrfs: use preallocated page for super block write David Sterba
2022-06-07 17:06 ` Boris Burkov
2022-06-08 17:49 ` Johannes Thumshirn
2022-06-09 7:30 ` Nikolay Borisov
2022-06-09 12:26 ` David Sterba
2022-06-09 12:36 ` Matthew Wilcox
2022-06-09 12:37 ` Nikolay Borisov
2022-06-16 14:37 ` [btrfs] 66a7a2412f: xfstests.btrfs.131.fail kernel test robot
2022-06-16 21:17 ` Matthew Wilcox [this message]
2022-06-16 22:00 ` David Sterba
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=Yqud1/SooVDamiuP@casper.infradead.org \
--to=willy@infradead.org \
--cc=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--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