From: kernel test robot <lkp@intel.com>
To: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-bluetooth@vger.kernel.org
Subject: [bluetooth-next:master 41/41] net/bluetooth/hci_sync.c:7510:6-13: WARNING: kzalloc should be used for cp, instead of kmalloc/memset
Date: Wed, 24 Dec 2025 03:21:59 +0800 [thread overview]
Message-ID: <202512240329.yzdnKHSG-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git master
head: 1d7a8fd800eb96f1175ddc3517822900c382cb80
commit: 1d7a8fd800eb96f1175ddc3517822900c382cb80 [41/41] Bluetooth: L2CAP: Add support for setting BT_PHY
config: i386-randconfig-051-20251223 (https://download.01.org/0day-ci/archive/20251224/202512240329.yzdnKHSG-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
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/202512240329.yzdnKHSG-lkp@intel.com/
cocci warnings: (new ones prefixed by >>)
>> net/bluetooth/hci_sync.c:7510:6-13: WARNING: kzalloc should be used for cp, instead of kmalloc/memset
vim +7510 net/bluetooth/hci_sync.c
7504
7505 int hci_le_set_phy(struct hci_conn *conn, u8 tx_phys, u8 rx_phys)
7506 {
7507 struct hci_dev *hdev = conn->hdev;
7508 struct hci_cp_le_set_phy *cp;
7509
> 7510 cp = kmalloc(sizeof(*cp), GFP_KERNEL);
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-12-23 19:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202512240329.yzdnKHSG-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.von.dentz@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).