From: kernel test robot <lkp@intel.com>
To: ishaangandhi <ishaangandhi@gmail.com>, davem@davemloft.net
Cc: kbuild-all@lists.01.org, ishaangandhi@gmail.com,
netdev@vger.kernel.org, willemb@google.com
Subject: Re: [PATCH] icmp: support rfc 5837
Date: Fri, 12 Mar 2021 11:10:53 +0800 [thread overview]
Message-ID: <202103121137.a6CqYs92-lkp@intel.com> (raw)
In-Reply-To: <20210312004706.33046-1-ishaangandhi@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2078 bytes --]
Hi ishaangandhi,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on net-next/master]
[also build test WARNING on net/master linus/master v5.12-rc2 next-20210311]
[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]
url: https://github.com/0day-ci/linux/commits/ishaangandhi/icmp-support-rfc-5837/20210312-084955
base: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git 1520929e26d54bc3c9e024ee91eee5a19c56b95b
config: i386-randconfig-s002-20210311 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.3-262-g5e674421-dirty
# https://github.com/0day-ci/linux/commit/42e5e7501eafeda575f91db23d34172d720316ab
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review ishaangandhi/icmp-support-rfc-5837/20210312-084955
git checkout 42e5e7501eafeda575f91db23d34172d720316ab
# save the attached .config to linux build tree
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=i386
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
"sparse warnings: (new ones prefixed by >>)"
>> net/ipv4/icmp.c:589:6: sparse: sparse: symbol 'icmp_identify_arrival_interface' was not declared. Should it be static?
net/ipv4/icmp.c: note: in included file (through include/linux/spinlock.h, include/linux/mmzone.h, include/linux/gfp.h, ...):
include/linux/bottom_half.h:32:30: sparse: sparse: context imbalance in 'icmp_reply' - different lock contexts for basic block
include/linux/bottom_half.h:32:30: sparse: sparse: context imbalance in '__icmp_send' - different lock contexts for basic block
Please review and possibly fold the followup patch.
---
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: 27954 bytes --]
next prev parent reply other threads:[~2021-03-12 3:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-12 0:47 [PATCH] icmp: support rfc 5837 ishaangandhi
2021-03-12 2:14 ` kernel test robot
2021-03-12 2:28 ` kernel test robot
2021-03-12 2:47 ` Willem de Bruijn
2021-03-12 3:10 ` kernel test robot [this message]
2021-03-12 3:10 ` [RFC PATCH] icmp: icmp_identify_arrival_interface() can be static kernel test robot
2021-03-15 8:29 ` [icmp] 42e5e7501e: BUG:KASAN:slab-out-of-bounds_in_pskb_expand_head 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=202103121137.a6CqYs92-lkp@intel.com \
--to=lkp@intel.com \
--cc=davem@davemloft.net \
--cc=ishaangandhi@gmail.com \
--cc=kbuild-all@lists.01.org \
--cc=netdev@vger.kernel.org \
--cc=willemb@google.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).