From: Qu Wenruo <wqu@suse•com>
To: dsterba@suse•cz, Mark Brown <broonie@kernel•org>
Cc: Boris Burkov <boris@bur•io>,
Johannes Thumshirn <johannes.thumshirn@wdc•com>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: build failure after merge of the btrfs-fixes tree
Date: Wed, 21 Jan 2026 10:03:05 +1030 [thread overview]
Message-ID: <33551776-18b2-4279-96c0-b7d1aadc0319@suse.com> (raw)
In-Reply-To: <20260120161838.GD26902@suse.cz>
在 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
next prev parent reply other threads:[~2026-01-20 23:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-20 12:07 linux-next: build failure after merge of the btrfs-fixes tree Mark Brown
2026-01-20 12:22 ` Johannes Thumshirn
2026-01-20 12:32 ` Mark Brown
2026-01-20 16:18 ` David Sterba
2026-01-20 23:33 ` Qu Wenruo [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-01-29 12:51 Mark Brown
2026-02-02 14:57 ` Mark Brown
2026-02-03 7:47 ` David Sterba
2024-03-17 22:17 Stephen Rothwell
2024-03-18 4:50 ` Anand Jain
2024-03-18 17:31 ` David Sterba
2024-03-18 18:58 ` David Sterba
[not found] <20200107082431.2b83a8ac@canb.auug.org.au>
2020-01-07 15:22 ` 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=33551776-18b2-4279-96c0-b7d1aadc0319@suse.com \
--to=wqu@suse$(echo .)com \
--cc=boris@bur$(echo .)io \
--cc=broonie@kernel$(echo .)org \
--cc=dsterba@suse$(echo .)cz \
--cc=johannes.thumshirn@wdc$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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