[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3a4b638a-f527-4d02-87ec-054ecb84ea0f@wdc.com>
Date: Tue, 20 Jan 2026 12:22:37 +0000
From: Johannes Thumshirn <Johannes.Thumshirn@....com>
To: Mark Brown <broonie@...nel.org>, David Sterba <dsterba@...e.cz>, Boris
Burkov <boris@....io>, WenRuo Qu <wqu@...e.com>
CC: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Linux Next
Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the btrfs-fixes tree
On 1/20/26 1:08 PM, Mark Brown wrote:
> Hi all,
>
> After merging the btrfs-fixes tree, today's linux-next build
> (arm64 defconfig) failed like this:
>
> /tmp/next/build/fs/btrfs/free-space-tree.c: In function 'btrfs_delete_orphan_free_space_entries':
> /tmp/next/build/fs/btrfs/free-space-tree.c:1765:9: error: implicit declaration of function 'BTRFS_PATH_AUTO_RELEASE'; did you mean 'BTRFS_PATH_AUTO_FREE'? [-Wimplicit-function-declaration]
> 1765 | BTRFS_PATH_AUTO_RELEASE(path);
> | ^~~~~~~~~~~~~~~~~~~~~~~
> | BTRFS_PATH_AUTO_FREE
> /tmp/next/build/fs/btrfs/free-space-tree.c:1765:33: error: 'path' undeclared (first use in this function)
> 1765 | BTRFS_PATH_AUTO_RELEASE(path);
> | ^~~~
> /tmp/next/build/fs/btrfs/free-space-tree.c:1765:33: note: each undeclared identifier is reported only once for each function it appears in
> /tmp/next/build/fs/btrfs/free-space-tree.c:1817:1: error: control reaches end of non-void function [-Werror=return-type]
> 1817 | }
> | ^
> cc1: some warnings being treated as errors
>
> Caused by commit
>
> 7fcf8455f610b (btrfs: reject new transactions if the fs is fully read-only)
>
> I have used the version from 20260119 instead.
>
This got introduced by
a08c5941d3ae ("btrfs: add mount time auto fix for orphan fst entries")
and 'BTRFS_PATH_AUTO_RELEASE()' got introduced by:
675af3c0fbd8 ("btrfs: introduce BTRFS_PATH_AUTO_RELEASE() helper")
which might be missing in for-next or btrfs-fixes?
Powered by blists - more mailing lists