From: kernel test robot <lkp@intel.com>
To: Wong Boon Jhee <wongboonjhee52@gmail.com>, netdev@vger.kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
horms@kernel.org, kuba@kernel.org,
Wong Boon Jhee <wongboonjhee52@gmail.com>
Subject: Re: [PATCH v9] net/ncsi: Fix use-after-free in NCSI teardown
Date: Sat, 10 Oct 2026 08:11:55 +0800 [thread overview]
Message-ID: <202610100859.YrkmZvhQ-lkp@intel.com> (raw)
In-Reply-To: <20261009082201.1424955-1-wongboonjhee52@gmail.com>
Hi Wong,
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 v7.3-rc6 next-20261008]
[cannot apply to horms-ipvs/master]
[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/Wong-Boon-Jhee/net-ncsi-Fix-use-after-free-in-NCSI-teardown/20261009-162201
base: net/main
patch link: https://lore.kernel.org/r/20261009082201.1424955-1-wongboonjhee52%40gmail.com
patch subject: [PATCH v9] net/ncsi: Fix use-after-free in NCSI teardown
config: i386-buildonly-randconfig-1005-20261010 (https://download.01.org/0day-ci/archive/20261010/202610100859.YrkmZvhQ-lkp@intel.com/config)
compiler: clang version 22.1.3 (https://github.com/llvm/llvm-project e9846648fd6183ee6d8cbdb4502213fcf902a211)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261010/202610100859.YrkmZvhQ-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/202610100859.YrkmZvhQ-lkp@intel.com/
All errors (new ones prefixed by >>):
>> net/ncsi/ncsi-manage.c:2101:19: error: use of undeclared identifier 'nc'
2101 | &np, &nc);
| ^~
net/ncsi/ncsi-manage.c:2103:38: error: use of undeclared identifier 'nc'
2103 | ncsi_send_netlink_timeout(nr, np, nc);
| ^~
2 errors generated.
vim +/nc +2101 net/ncsi/ncsi-manage.c
2078
2079 void ncsi_unregister_dev(struct ncsi_dev *nd)
2080 {
2081 struct ncsi_dev_priv *ndp = TO_NCSI_DEV_PRIV(nd);
2082 struct ncsi_package *np, *tmp;
2083 struct vlan_vid *vlan, *vlan_tmp;
2084 unsigned long flags;
2085 int i;
2086
2087 ncsi_unregister_dev_prepare(nd);
2088 for (i = 0; i < ARRAY_SIZE(ndp->requests); i++) {
2089 struct ncsi_request *nr = &ndp->requests[i];
2090
2091 if (!nr->used)
2092 continue;
2093
2094 if (nr->flags == NCSI_REQ_FLAG_NETLINK_DRIVEN && nr->cmd) {
2095 struct ncsi_cmd_pkt *cmd = (struct ncsi_cmd_pkt *)
2096 skb_network_header(nr->cmd);
2097
2098 rcu_read_lock();
2099 ncsi_find_package_and_channel(ndp,
2100 cmd->cmd.common.channel,
> 2101 &np, &nc);
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-10-10 0:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-09 8:22 [PATCH v9] net/ncsi: Fix use-after-free in NCSI teardown Wong Boon Jhee
2026-10-09 8:24 ` netdev-bot+sinfo
2026-10-10 0:11 ` kernel test robot
2026-10-10 0:11 ` kernel test robot [this message]
2026-10-10 10:35 ` 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=202610100859.YrkmZvhQ-lkp@intel.com \
--to=lkp@intel.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=llvm@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=wongboonjhee52@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