linux-kernel - 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>] [day] [month] [year] [list]

Message-ID: <aXtXw3_wMDnrrOxW@sirena.org.uk>
Date: Thu, 29 Jan 2026 12:51:15 +0000
From: Mark Brown <broonie@...nel.org>
To: David Sterba <dsterba@...e.cz>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: linux-next: build failure after merge of the btrfs-fixes tree

Hi all,

After merging the btrfs-fixes tree, today's linux-next build
(arm64 defconfig) failed like this:

/tmp/next/build/fs/btrfs/bio.c: In function 'btrfs_split_bio':
/tmp/next/build/fs/btrfs/bio.c:102:13: error: 'struct btrfs_bio' has no member named 'can_use_append'
  102 |         bbio->can_use_append = orig_bbio->can_use_append;
      |             ^~
/tmp/next/build/fs/btrfs/bio.c:102:41: error: 'struct btrfs_bio' has no member named 'can_use_append'
  102 |         bbio->can_use_append = orig_bbio->can_use_append;
      |                                         ^~
/tmp/next/build/fs/btrfs/bio.c:104:13: error: 'struct btrfs_bio' has no member named 'is_remap'
  104 |         bbio->is_remap = orig_bbio->is_remap;
      |             ^~
/tmp/next/build/fs/btrfs/bio.c:104:35: error: 'struct btrfs_bio' has no member named 'is_remap'
  104 |         bbio->is_remap = orig_bbio->is_remap;
      |                                   ^~

Caused by commit

   4b40b1c47f937 (btrfs: fix copying the flags of btrfs_bio after split)

I have used the version from 20260128 instead.