linux-kernel - Re: [btrfs] 66a7a2412f: xfstests.btrfs.131.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] [day] [month] [year] [list]

Message-ID: <20220616220036.GF20633@twin.jikos.cz>
Date:   Fri, 17 Jun 2022 00:00:36 +0200
From:   David Sterba <dsterba@...e.cz>
To:     Matthew Wilcox <willy@...radead.org>
Cc:     kernel test robot <oliver.sang@...el.com>,
        David Sterba <dsterba@...e.com>, 0day robot <lkp@...el.com>,
        LKML <linux-kernel@...r.kernel.org>, linux-btrfs@...r.kernel.org,
        lkp@...ts.01.org
Subject: Re: [btrfs]  66a7a2412f: xfstests.btrfs.131.fail

On Thu, Jun 16, 2022 at 10:17:11PM +0100, Matthew Wilcox wrote:
> 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?

The build bot picks up the branch with some delay, I've removed it from
the pushed branches. It's interesting to see that using the page cache
vs direct write does have effects in tests, so it would need to be
unified in kernel and user space.