linux-kernel - Re: linux-next: build failure after merge of the btrfs tree

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: <20250227094042.GZ5777@suse.cz>
Date: Thu, 27 Feb 2025 10:40:42 +0100
From: David Sterba <dsterba@...e.cz>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: David Sterba <dsterba@...e.com>, Goldwyn Rodrigues <rgoldwyn@...e.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 tree

On Thu, Feb 27, 2025 at 10:32:14AM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the btrfs tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
> 
> fs/btrfs/extent_io.c: In function 'btrfs_set_folio_subpage':
> fs/btrfs/extent_io.c:874:45: error: passing argument 2 of 'btrfs_is_subpage' from incompatible pointer type [-Wincompatible-pointer-types]
>   874 |         if (!btrfs_is_subpage(fs_info, folio->mapping))
>       |                                        ~~~~~^~~~~~~~~
>       |                                             |
>       |                                             struct address_space *
> In file included from fs/btrfs/extent_io.c:26:
> fs/btrfs/subpage.h:95:51: note: expected 'struct folio *' but argument is of type 'struct address_space *'
>    95 |                                     struct folio *folio)
>       |                                     ~~~~~~~~~~~~~~^~~~~
> 
> Caused by commit
> 
>   40524fd05deb ("btrfs: kill EXTENT_FOLIO_PRIVATE")
> 
> I have used the btffs tree from next-20250226 for today.

Fixed in in today's for-next snapshot.