linux-kernel - linux-next: build failure after merge of the device-mapper 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 for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 11 Feb 2021 14:36:55 +1100
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Alasdair G Kergon <agk@...hat.com>,
        Mike Snitzer <snitzer@...hat.com>
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 device-mapper tree

Hi all,

After merging the device-mapper tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:

drivers/md/dm-linear.c:234:3: error: 'struct target_type' has no member named 'report_zones'
  234 |  .report_zones = linear_report_zones,
      |   ^~~~~~~~~~~~
drivers/md/dm-crypt.c:3585:3: error: 'struct target_type' has no member named 'report_zones'
 3585 |  .report_zones = crypt_report_zones,
      |   ^~~~~~~~~~~~

Caused by commit

  7defd0da9dd2 ("dm: simplify target code conditional on CONFIG_BLK_DEV_ZONED")

The report_zones members existence is guarded by CONFIG_BLK_DEV_ZONED.

I have used the device-mapper tree from next-20210210 for today.

-- 
Cheers,
Stephen Rothwell

Content of type "application/pgp-signature" skipped