From: kernel test robot <lkp@intel.com>
To: Neeraj Sanjay Kale <neeraj.sanjaykale@nxp.com>,
marcel@holtmann.org, luiz.dentz@gmail.com
Cc: oe-kbuild-all@lists.linux.dev, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org, amitkumar.karwar@nxp.com,
sherry.sun@nxp.com, dmitrii.lebed@nxp.com,
neeraj.sanjaykale@nxp.com
Subject: Re: [PATCH v1 07/11] Bluetooth: btnxpuart: Add device authentication
Date: Thu, 20 Nov 2025 22:46:25 +0800 [thread overview]
Message-ID: <202511202234.PN8Zn4v7-lkp@intel.com> (raw)
In-Reply-To: <20251118142025.1982263-8-neeraj.sanjaykale@nxp.com>
Hi Neeraj,
kernel test robot noticed the following build warnings:
[auto build test WARNING on bluetooth/master]
[also build test WARNING on bluetooth-next/master linus/master v6.18-rc6]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Neeraj-Sanjay-Kale/Bluetooth-btnxpuart-Add-firmware-metadata-parsing-for-secure-interface/20251118-223605
base: https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth.git master
patch link: https://lore.kernel.org/r/20251118142025.1982263-8-neeraj.sanjaykale%40nxp.com
patch subject: [PATCH v1 07/11] Bluetooth: btnxpuart: Add device authentication
config: i386-randconfig-061-20251120 (https://download.01.org/0day-ci/archive/20251120/202511202234.PN8Zn4v7-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251120/202511202234.PN8Zn4v7-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202511202234.PN8Zn4v7-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
drivers/bluetooth/btnxpuart.c:1433:55: sparse: sparse: restricted __le32 degrades to integer
drivers/bluetooth/btnxpuart.c:1441:27: sparse: sparse: restricted __le32 degrades to integer
drivers/bluetooth/btnxpuart.c:1446:47: sparse: sparse: restricted __le32 degrades to integer
drivers/bluetooth/btnxpuart.c:1447:32: sparse: sparse: restricted __le32 degrades to integer
drivers/bluetooth/btnxpuart.c:1450:26: sparse: sparse: restricted __le32 degrades to integer
drivers/bluetooth/btnxpuart.c:1529:17: sparse: sparse: restricted __le32 degrades to integer
>> drivers/bluetooth/btnxpuart.c:1758:64: sparse: sparse: incorrect type in argument 2 (different base types) @@ expected unsigned short [usertype] chipid @@ got restricted __le16 const [usertype] chip_id @@
drivers/bluetooth/btnxpuart.c:1758:64: sparse: expected unsigned short [usertype] chipid
drivers/bluetooth/btnxpuart.c:1758:64: sparse: got restricted __le16 const [usertype] chip_id
>> drivers/bluetooth/btnxpuart.c:1759:58: sparse: sparse: incorrect type in argument 3 (different base types) @@ expected unsigned char [usertype] loader_ver @@ got restricted __le16 const [usertype] device_flags @@
drivers/bluetooth/btnxpuart.c:1759:58: sparse: expected unsigned char [usertype] loader_ver
drivers/bluetooth/btnxpuart.c:1759:58: sparse: got restricted __le16 const [usertype] device_flags
>> drivers/bluetooth/btnxpuart.c:2114:25: sparse: sparse: incorrect type in initializer (different base types) @@ expected restricted __le16 [usertype] len @@ got unsigned short [usertype] @@
drivers/bluetooth/btnxpuart.c:2114:25: sparse: expected restricted __le16 [usertype] len
drivers/bluetooth/btnxpuart.c:2114:25: sparse: got unsigned short [usertype]
drivers/bluetooth/btnxpuart.c:2186:25: sparse: sparse: incorrect type in initializer (different base types) @@ expected restricted __le16 [usertype] len @@ got unsigned short [usertype] @@
drivers/bluetooth/btnxpuart.c:2186:25: sparse: expected restricted __le16 [usertype] len
drivers/bluetooth/btnxpuart.c:2186:25: sparse: got unsigned short [usertype]
vim +1758 drivers/bluetooth/btnxpuart.c
1746
1747 /* Secure Interface */
1748 static int nxp_get_pub_key(struct hci_dev *hdev,
1749 const struct nxp_tls_device_info *device_info,
1750 u8 ecdsa_pub_key[NXP_FW_ECDSA_PUBKEY_SIZE])
1751 {
1752 struct btnxpuart_dev *nxpdev = hci_get_drvdata(hdev);
1753 const char *fw_name;
1754
1755 if (ecdsa_pub_key[0] == 0x04)
1756 return 0;
1757
> 1758 fw_name = nxp_get_fw_name_from_chipid(hdev, device_info->chip_id,
> 1759 device_info->device_flags);
1760 if (nxp_request_firmware(hdev, fw_name, NULL))
1761 return -ENOENT;
1762
1763 nxp_process_fw_meta_data(hdev, nxpdev->fw);
1764 release_firmware(nxpdev->fw);
1765 memset(nxpdev->fw_name, 0, sizeof(nxpdev->fw_name));
1766
1767 if (memcmp(nxpdev->crypto.fw_uuid, device_info->uuid, 16) ||
1768 nxpdev->crypto.ecdsa_public[0] != 0x04) {
1769 bt_dev_err(hdev,
1770 "UUID check failed while trying to read ECDSA public key from FW.");
1771 return -EBADF;
1772 }
1773
1774 memcpy(ecdsa_pub_key, nxpdev->crypto.ecdsa_public, 65);
1775
1776 return 0;
1777 }
1778
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-11-20 14:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-18 14:20 [PATCH v1 00/11] Bluetooth: btnxpuart: Add secure interface support for NXP chipsets Neeraj Sanjay Kale
2025-11-18 14:20 ` [PATCH v1 01/11] Bluetooth: btnxpuart: Add firmware metadata parsing for secure interface Neeraj Sanjay Kale
2025-11-18 15:07 ` Bluetooth: btnxpuart: Add secure interface support for NXP chipsets bluez.test.bot
2025-11-20 7:12 ` [PATCH v1 01/11] Bluetooth: btnxpuart: Add firmware metadata parsing for secure interface kernel test robot
2025-11-18 14:20 ` [PATCH v1 02/11] Bluetooth: btnxpuart: Print FW version and enable chip specific features Neeraj Sanjay Kale
2025-11-18 14:20 ` [PATCH v1 03/11] Bluetooth: btnxpuart: Add secure interface TLS authentication support Neeraj Sanjay Kale
2025-11-18 14:20 ` [PATCH v1 04/11] Bluetooth: btnxpuart: Implement TLS authentication crypto framework Neeraj Sanjay Kale
2025-11-18 14:20 ` [PATCH v1 05/11] Bluetooth: btnxpuart: Add TLS host hello handshake implementation Neeraj Sanjay Kale
2025-11-22 3:31 ` kernel test robot
2025-11-18 14:20 ` [PATCH v1 06/11] Bluetooth: btnxpuart: Add TLS device hello processing Neeraj Sanjay Kale
2025-11-18 14:20 ` [PATCH v1 07/11] Bluetooth: btnxpuart: Add device authentication Neeraj Sanjay Kale
2025-11-20 14:46 ` kernel test robot [this message]
2025-11-22 11:03 ` kernel test robot
2025-11-18 14:20 ` [PATCH v1 08/11] Bluetooth: btnxpuart: Derive traffic keys from TLS 1.3 handshake Neeraj Sanjay Kale
2025-11-18 14:20 ` [PATCH v1 09/11] Bluetooth: btnxpuart: Add command encryption for sensitive HCI commands Neeraj Sanjay Kale
2025-11-20 8:40 ` kernel test robot
2025-11-18 14:20 ` [PATCH v1 10/11] Bluetooth: btnxpuart: Add encrypted event handling Neeraj Sanjay Kale
2025-11-18 14:20 ` [PATCH v1 11/11] Bluetooth: btnxpuart: Select crypto algorithms for secure interface Neeraj Sanjay Kale
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=202511202234.PN8Zn4v7-lkp@intel.com \
--to=lkp@intel.com \
--cc=amitkumar.karwar@nxp.com \
--cc=dmitrii.lebed@nxp.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=neeraj.sanjaykale@nxp.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sherry.sun@nxp.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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