linux-kernel - Re: linux-next: build failure after merge of the btrfs-fixes 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] [thread-next>] [day] [month] [year] [list]

Message-ID: <d9d6d334-7d50-4d36-a03e-f2f6811e0ecb@oracle.com>
Date: Mon, 18 Mar 2024 10:20:54 +0530
From: Anand Jain <anand.jain@...cle.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>, David Sterba <dsterba@...e.cz>
Cc: David Sterba <dsterba@...e.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        Christian Brauner <brauner@...nel.org>
Subject: Re: linux-next: build failure after merge of the btrfs-fixes tree



On 3/18/24 03:47, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the btrfs-fixes tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
> 
> fs/btrfs/volumes.c: In function 'btrfs_scan_one_device':
> fs/btrfs/volumes.c:1413:55: error: 'bdev_handle' undeclared (first use in this function)
>   1413 |         if (btrfs_skip_registration(disk_super, path, bdev_handle->bdev->bd_dev,
>        |                                                       ^~~~~~~~~~~
> fs/btrfs/volumes.c:1413:55: note: each undeclared identifier is reported only once for each function it appears in
> 
> Caused by commit
> 
>    cc019bc0d55b ("btrfs: do not skip re-registration for the mounted device")
> 
> I have used the btrfs-fixes tree from next-20240315 for today.
> 


> This is actually caused by an interaction with commit
> 
>    9ae061cf2a46 ("btrfs: port device access to file")
> 

Ah, unaware of this change. Thanks for the report.
A new fix, built on top of this change, has now been sent out.

As the Linux-next branch no longer has the commit cc019bc0d55b,
I've sent out the entire patch again.

https://lore.kernel.org/linux-btrfs/57a63f9905549f22618a85991b775fba76104412.1710732026.git.anand.jain@oracle.com/


Thanks, Anand

> which has been in Linus' tree since March 12 (and linux-next since Feb 26).