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

Message-ID: <20240501111917.23e2b0f2@canb.auug.org.au>
Date: Wed, 1 May 2024 11:19:17 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Marcel Holtmann <marcel@...tmann.org>, Johan Hedberg
 <johan.hedberg@...il.com>
Cc: Luiz Augusto von Dentz <luiz.von.dentz@...el.com>, Sungwoo Kim
 <iam@...g-woo.kim>, 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 bluetooth tree

Hi all,

After merging the bluetooth tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:

net/bluetooth/hci_core.c: In function 'hci_release_dev':
net/bluetooth/hci_core.c:2831:9: error: implicit declaration of function 'msft_release'; did you mean 'dst_release'? [-Werror=implicit-function-declaration]
 2831 |         msft_release(hdev);
      |         ^~~~~~~~~~~~
      |         dst_release
cc1: some warnings being treated as errors

Caused by commit

  d85d07aefca7 ("Bluetooth: msft: fix slab-use-after-free in msft_do_close()")

(though I don't see why)

I have used the bluetooth tree from next-20240430 for today.

-- 
Cheers,
Stephen Rothwell

Content of type "application/pgp-signature" skipped