From: kernel test robot <lkp@intel.com>
To: Dudu Lu <phx0fer@gmail.com>, netdev@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
Dudu Lu <phx0fer@gmail.com>
Subject: Re: [PATCH] nfc: nci: Add skb length validation in nci_core_init_rsp_packet
Date: Thu, 30 Apr 2026 09:43:02 +0800 [thread overview]
Message-ID: <202604300902.FjrlfrkQ-lkp@intel.com> (raw)
In-Reply-To: <20260413090102.77980-1-phx0fer@gmail.com>
Hi Dudu,
kernel test robot noticed the following build errors:
[auto build test ERROR on net/main]
[also build test ERROR on net-next/main linus/master horms-ipvs/master v7.1-rc1 next-20260429]
[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/Dudu-Lu/nfc-nci-Add-skb-length-validation-in-nci_core_init_rsp_packet/20260423-210923
base: net/main
patch link: https://lore.kernel.org/r/20260413090102.77980-1-phx0fer%40gmail.com
patch subject: [PATCH] nfc: nci: Add skb length validation in nci_core_init_rsp_packet
config: arm64-randconfig-001-20260430 (https://download.01.org/0day-ci/archive/20260430/202604300902.FjrlfrkQ-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 8.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260430/202604300902.FjrlfrkQ-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/202604300902.FjrlfrkQ-lkp@intel.com/
All errors (new ones prefixed by >>):
>> net/nfc/nci/rsp.c:1:2: error: expected identifier or '(' before 'if'
if (skb->len < sizeof(*rsp)) {
^~
net/nfc/nci/rsp.c:5:2: error: expected identifier or '(' before 'if'
if (skb->len < 6 + rsp_1->num_supported_rf_interfaces +
^~
net/nfc/nci/rsp.c:10:2: error: expected identifier or '(' before 'if'
if (skb->len < sizeof(*rsp_1))
^~
vim +1 net/nfc/nci/rsp.c
> 1 if (skb->len < sizeof(*rsp)) {
2 pr_err("short NCI_CORE_INIT_RSP v2 packet\n");
3 return NCI_STATUS_SYNTAX_ERROR;
4 }
5 if (skb->len < 6 + rsp_1->num_supported_rf_interfaces +
6 sizeof(*rsp_2)) {
7 pr_err("short NCI_CORE_INIT_RSP v1 packet\n");
8 return NCI_STATUS_SYNTAX_ERROR;
9 }
10 if (skb->len < sizeof(*rsp_1))
11 return NCI_STATUS_SYNTAX_ERROR;
12 // SPDX-License-Identifier: GPL-2.0-only
13 /*
14 * The NFC Controller Interface is the communication protocol between an
15 * NFC Controller (NFCC) and a Device Host (DH).
16 *
17 * Copyright (C) 2011 Texas Instruments, Inc.
18 *
19 * Written by Ilan Elias <ilane@ti.com>
20 *
21 * Acknowledgements:
22 * This file is based on hci_event.c, which was written
23 * by Maxim Krasnyansky.
24 */
25
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-04-30 1:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-13 9:01 [PATCH] nfc: nci: Add skb length validation in nci_core_init_rsp_packet Dudu Lu
2026-04-30 1:43 ` kernel test robot [this message]
2026-04-30 3:03 ` kernel 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=202604300902.FjrlfrkQ-lkp@intel.com \
--to=lkp@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pabeni@redhat.com \
--cc=phx0fer@gmail.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