[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <33551776-18b2-4279-96c0-b7d1aadc0319@suse.com>
Date: Wed, 21 Jan 2026 10:03:05 +1030
From: Qu Wenruo <wqu@...e.com>
To: dsterba@...e.cz, Mark Brown <broonie@...nel.org>
Cc: Boris Burkov <boris@....io>,
Johannes Thumshirn <johannes.thumshirn@....com>,
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
在 2026/1/21 02:48, David Sterba 写道:
> On Tue, Jan 20, 2026 at 12:07:58PM +0000, 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.
>
> Sorry, I'll drop the patch from next-fixes.
Or should I update the patch to use traditional manual path releasing?
As this one may need to be backported for older kernels.
Thanks,
Qu
Powered by blists - more mailing lists