From: kbuild test robot <lkp@intel.com>
To: Eric Dumazet <edumazet@google.com>
Cc: kbuild-all@01.org, netdev@vger.kernel.org
Subject: [net:master 11/11] net//ipv4/igmp.c:2157:2: error: implicit declaration of function 'ip_sf_list_clear_all'
Date: Thu, 23 May 2019 10:12:13 +0800 [thread overview]
Message-ID: <201905231010.QXl9S1Un%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1644 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git master
head: 3580d04aa674383c42de7b635d28e52a1e5bc72c
commit: 3580d04aa674383c42de7b635d28e52a1e5bc72c [11/11] ipv4/igmp: fix another memory leak in igmpv3_del_delrec()
config: i386-randconfig-i0-201920 (attached as .config)
compiler: gcc-5 (Debian 5.5.0-3) 5.4.1 20171010
reproduce:
git checkout 3580d04aa674383c42de7b635d28e52a1e5bc72c
# save the attached .config to linux build tree
make ARCH=i386
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
net//ipv4/igmp.c: In function 'ip_mc_clear_src':
>> net//ipv4/igmp.c:2157:2: error: implicit declaration of function 'ip_sf_list_clear_all' [-Werror=implicit-function-declaration]
ip_sf_list_clear_all(tomb);
^
cc1: some warnings being treated as errors
vim +/ip_sf_list_clear_all +2157 net//ipv4/igmp.c
2142
2143 static void ip_mc_clear_src(struct ip_mc_list *pmc)
2144 {
2145 struct ip_sf_list *tomb, *sources;
2146
2147 spin_lock_bh(&pmc->lock);
2148 tomb = pmc->tomb;
2149 pmc->tomb = NULL;
2150 sources = pmc->sources;
2151 pmc->sources = NULL;
2152 pmc->sfmode = MCAST_EXCLUDE;
2153 pmc->sfcount[MCAST_INCLUDE] = 0;
2154 pmc->sfcount[MCAST_EXCLUDE] = 1;
2155 spin_unlock_bh(&pmc->lock);
2156
> 2157 ip_sf_list_clear_all(tomb);
2158 ip_sf_list_clear_all(sources);
2159 }
2160
---
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: 33133 bytes --]
reply other threads:[~2019-05-23 2:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201905231010.QXl9S1Un%lkp@intel.com \
--to=lkp@intel.com \
--cc=edumazet@google.com \
--cc=kbuild-all@01.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.