From: Anand Jain <anand.jain@oracle•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>, David Sterba <dsterba@suse•cz>
Cc: David Sterba <dsterba@suse•com>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>,
Christian Brauner <brauner@kernel•org>
Subject: Re: linux-next: build failure after merge of the btrfs-fixes tree
Date: Mon, 18 Mar 2024 10:20:54 +0530 [thread overview]
Message-ID: <d9d6d334-7d50-4d36-a03e-f2f6811e0ecb@oracle.com> (raw)
In-Reply-To: <20240318091755.1d0f696f@canb.auug.org.au>
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).
next prev parent reply other threads:[~2024-03-18 4:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-17 22:17 linux-next: build failure after merge of the btrfs-fixes tree Stephen Rothwell
2024-03-18 4:50 ` Anand Jain [this message]
2024-03-18 17:31 ` David Sterba
2024-03-18 18:58 ` David Sterba
-- 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
2026-01-20 12:07 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
[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=d9d6d334-7d50-4d36-a03e-f2f6811e0ecb@oracle.com \
--to=anand.jain@oracle$(echo .)com \
--cc=brauner@kernel$(echo .)org \
--cc=dsterba@suse$(echo .)com \
--cc=dsterba@suse$(echo .)cz \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/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