From: kbuild test robot <lkp@intel.com>
To: spoorthix.k@intel.com
Cc: kbuild-all@01.org, linux-bluetooth@vger.kernel.org, marcel@holtmann.org
Subject: Re: [PATCH] Add Support to use Resolving List
Date: Fri, 30 Aug 2019 03:11:25 +0800 [thread overview]
Message-ID: <201908300226.hYCUXCu2%lkp@intel.com> (raw)
In-Reply-To: <1567063341-12330-1-git-send-email-spoorthix.k@intel.com>
[-- Attachment #1: Type: text/plain, Size: 3904 bytes --]
Hi,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on linus/master]
[cannot apply to v5.3-rc6 next-20190829]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/spoorthix-k-intel-com/Add-Support-to-use-Resolving-List/20190830-003531
config: m68k-allmodconfig (attached as .config)
compiler: m68k-linux-gcc (GCC) 7.4.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
GCC_VERSION=7.4.0 make.cross ARCH=m68k
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
net/bluetooth/hci_request.c: In function 'update_resolve_list':
>> net/bluetooth/hci_request.c:735:1: warning: no return statement in function returning non-void [-Wreturn-type]
}
^
net/bluetooth/hci_request.c: In function 'hci_req_add_le_passive_scan':
>> net/bluetooth/hci_request.c:684:25: warning: 'params' may be used uninitialized in this function [-Wmaybe-uninitialized]
cp.bdaddr_type = params->addr_type;
~~~~~~^~~~~~~~~~~
net/bluetooth/hci_request.c:694:26: note: 'params' was declared here
struct hci_conn_params *params;
^~~~~~
vim +735 net/bluetooth/hci_request.c
672
673 static void add_to_resolve_list(struct hci_request *req,
674 struct hci_conn_params *params)
675 {
676 struct hci_cp_le_add_to_resolv_list cp;
677 struct bdaddr_list_with_irk *entry;
678
679 entry = kzalloc(sizeof(*entry), GFP_KERNEL);
680 if (!entry)
681 return;
682 memset(&cp, 0, sizeof(cp));
683
> 684 cp.bdaddr_type = params->addr_type;
685 bacpy(&cp.bdaddr, ¶ms->addr);
686 memcpy(entry->peer_irk, cp.peer_irk, 16);
687 memcpy(entry->local_irk, cp.local_irk, 16);
688 hci_req_add(req, HCI_OP_LE_ADD_TO_RESOLV_LIST, sizeof(cp), &cp);
689 }
690
691 static u8 update_resolve_list(struct hci_request *req)
692 {
693 struct hci_dev *hdev = req->hdev;
694 struct hci_conn_params *params;
695 struct bdaddr_list *b;
696 int err;
697 u8 resolve_list_entries = 0;
698
699 list_for_each_entry(b, &hdev->le_resolv_list, list) {
700 /* Cannot Remove or add the device to the Resolving list
701 * whenever there is an outstanding connection.
702 */
703 if (!hci_pend_le_action_lookup(&hdev->pend_le_conns,
704 &b->bdaddr, b->bdaddr_type) &&
705 !hci_pend_le_action_lookup(&hdev->pend_le_reports,
706 &b->bdaddr, b->bdaddr_type)) {
707 struct hci_cp_le_del_from_resolv_list cp;
708
709 cp.bdaddr_type = b->bdaddr_type;
710 bacpy(&cp.bdaddr, &b->bdaddr);
711
712 hci_req_add(req, HCI_OP_LE_DEL_FROM_RESOLV_LIST,
713 sizeof(cp), &cp);
714 continue;
715 }
716
717 if (hci_find_irk_by_addr(hdev, &b->bdaddr, b->bdaddr_type)) {
718 /* Add device to resolving list */
719 resolve_list_entries++;
720 add_to_resolve_list(req, params);
721 }
722
723 if (hci_bdaddr_list_lookup(&hdev->le_resolv_list,
724 ¶ms->addr, params->addr_type))
725 continue;
726
727 if (resolve_list_entries >= hdev->le_resolv_list_size) {
728 err = smp_generate_rpa(hdev, hdev->irk, &hdev->rpa);
729 if (err < 0)
730 BT_ERR("%s failed to generate new RPA",
731 hdev->name);
732 }
733 resolve_list_entries++;
734 }
> 735 }
736
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 50935 bytes --]
next prev parent reply other threads:[~2019-08-29 19:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-29 7:22 [PATCH] Add Support to use Resolving List spoorthix.k
2019-08-29 19:11 ` kbuild test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-09-18 10:36 [PATCH] Add support to use Resolving list spoorthix.k
2019-09-27 7:07 ` Marcel Holtmann
2019-09-27 7:14 ` Johan Hedberg
2019-08-30 8:13 [PATCH] Add Support " spoorthix.k
2019-09-05 15:43 ` Marcel Holtmann
2019-08-14 8:18 [PATCH] Add support to use resolving list spoorthix.k
2019-08-15 6:56 ` Marcel Holtmann
2019-08-12 10:49 spoorthix.k
2019-08-12 18:15 ` kbuild test robot
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=201908300226.hYCUXCu2%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=spoorthix.k@intel.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;
as well as URLs for NNTP newsgroup(s).