From: kernel test robot <lkp@intel.com>
To: Jeremy Kerr <jk@codeconstruct.com.au>, netdev@vger.kernel.org
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
Jakub Kicinski <kuba@kernel.org>,
Matt Johnston <matt@codeconstruct.com.au>,
Andrew Jeffery <andrew@aj.id.au>
Subject: Re: [PATCH net-next 2/3] mctp: Add flow extension to skb
Date: Thu, 28 Oct 2021 21:09:45 +0800 [thread overview]
Message-ID: <202110282116.5UUTFgkX-lkp@intel.com> (raw)
In-Reply-To: <20211028061833.2390354-2-jk@codeconstruct.com.au>
[-- Attachment #1: Type: text/plain, Size: 2183 bytes --]
Hi Jeremy,
I love your patch! Yet something to improve:
[auto build test ERROR on net-next/master]
url: https://github.com/0day-ci/linux/commits/Jeremy-Kerr/mctp-Return-new-key-from-mctp_alloc_local_tag/20211028-142024
base: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git 5a48585d7ec1d0e1e83539d56846c1e513ef66ea
config: i386-buildonly-randconfig-r005-20211027 (attached as .config)
compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project 5db7568a6a1fcb408eb8988abdaff2a225a8eb72)
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/0day-ci/linux/commit/587328c0d21081a26183368afcf4874a210889c3
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Jeremy-Kerr/mctp-Return-new-key-from-mctp_alloc_local_tag/20211028-142024
git checkout 587328c0d21081a26183368afcf4874a210889c3
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 ARCH=i386
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> net/core/skbuff.c:6572:5: error: 'CONFIG_MCTP_FLOWS' is not defined, evaluates to 0 [-Werror,-Wundef]
#if CONFIG_MCTP_FLOWS
^
1 error generated.
vim +/CONFIG_MCTP_FLOWS +6572 net/core/skbuff.c
6556
6557 void __skb_ext_put(struct skb_ext *ext)
6558 {
6559 /* If this is last clone, nothing can increment
6560 * it after check passes. Avoids one atomic op.
6561 */
6562 if (refcount_read(&ext->refcnt) == 1)
6563 goto free_now;
6564
6565 if (!refcount_dec_and_test(&ext->refcnt))
6566 return;
6567 free_now:
6568 #ifdef CONFIG_XFRM
6569 if (__skb_ext_exist(ext, SKB_EXT_SEC_PATH))
6570 skb_ext_put_sp(skb_ext_get_ptr(ext, SKB_EXT_SEC_PATH));
6571 #endif
> 6572 #if CONFIG_MCTP_FLOWS
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 40132 bytes --]
next prev parent reply other threads:[~2021-10-28 13:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-28 6:18 [PATCH net-next 1/3] mctp: Return new key from mctp_alloc_local_tag Jeremy Kerr
2021-10-28 6:18 ` [PATCH net-next 2/3] mctp: Add flow extension to skb Jeremy Kerr
2021-10-28 12:02 ` kernel test robot
2021-10-28 13:09 ` kernel test robot [this message]
2021-10-28 6:18 ` [PATCH net-next 3/3] mctp: Pass flow data & flow release events to drivers Jeremy Kerr
2021-10-28 12:20 ` 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=202110282116.5UUTFgkX-lkp@intel.com \
--to=lkp@intel.com \
--cc=andrew@aj.id.au \
--cc=jk@codeconstruct.com.au \
--cc=kbuild-all@lists.01.org \
--cc=kuba@kernel.org \
--cc=llvm@lists.linux.dev \
--cc=matt@codeconstruct.com.au \
--cc=netdev@vger.kernel.org \
/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).