netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Roeseler <andreas.a.roeseler@gmail.com>
To: Network Development <netdev@vger.kernel.org>
Cc: David Miller <davem@davemloft.net>,
	Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>,
	Jakub Kicinski <kuba@kernel.org>,
	David Ahern <dsahern@kernel.org>
Subject: Re: [PATCH V4 net-next 5/5] icmp: add response to RFC 8335 PROBE messages
Date: Wed, 17 Mar 2021 22:11:47 -0500	[thread overview]
Message-ID: <72c4ccfc219c830f1d289c3d4c8a43aec6e94877.camel@gmail.com> (raw)
In-Reply-To: <202103150433.OwOTmI15-lkp@intel.com>

On Mon, 2021-03-15 at 04:35 +0800, kernel test robot wrote:
> Hi Andreas,
> 
> [FYI, it's a private test report for your RFC patch.]
> [auto build test ERROR on net-next/master]
> 
> url:    
> https://github.com/0day-ci/linux/commits/Andreas-Roeseler/add-support-for-RFC-8335-PROBE/20210315-005052
> base:   
> https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git 6f
> 1629093399303bf19d6fcd5144061d1e25ec23
> config: mips-allmodconfig (attached as .config)
> compiler: mips-linux-gcc (GCC) 9.3.0
> 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/54d9928f1734e7b3511b945a2ce912b931a07776
>         git remote add linux-review https://github.com/0day-ci/linux
>         git fetch --no-tags linux-review Andreas-Roeseler/add-
> support-for-RFC-8335-PROBE/20210315-005052
>         git checkout 54d9928f1734e7b3511b945a2ce912b931a07776
>         # save the attached .config to linux build tree
>         COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0
> make.cross ARCH=mips 
> 
> 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 >>):
> 
>    mips-linux-ld: net/ipv4/icmp.o: in function `icmp_echo':
> > > icmp.c:(.text.icmp_echo+0x658): undefined reference to
> > > `ipv6_dev_find'
> 
> ---
> 0-DAY CI Kernel Test Service, Intel Corporation
> https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

I'm still learning the ropes of kernel development and I was wondering
if someone could help me figure out what is causing this error.

The file compiles when compiling with allyesconfig or olddefconfig, but
it cannot find the ipv6_dev_find() function when compiling with
allmodconfig and returns the error seen above. I am including
<include/net/addrconf.h> which declares ipv6_dev_find(), and the
function is defined and exported using EXPORT_SYMBOL in
<net/ipv6/addrconf.c>. I've tried declaring the function via extern in
<include/net/icmp.h> and in <net/ipv4/icmp.c>, but neither have
resolved the error and checkpatch.pl explicitly warns against using
extern calls in .c files.

Is there something that I'm not understanding about compiling kernel
components modularly? How do I avoid this error?



  parent reply	other threads:[~2021-03-18  3:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-14 16:48 [PATCH V4 net-next 0/5] add support for RFC 8335 PROBE Andreas Roeseler
2021-03-14 16:48 ` [PATCH V4 net-next 1/5] icmp: " Andreas Roeseler
2021-03-14 16:48 ` [PATCH V4 net-next 2/5] ICMPV6: " Andreas Roeseler
2021-03-14 16:48 ` [PATCH V4 net-next 3/5] net: add sysctl for enabling RFC 8335 PROBE messages Andreas Roeseler
2021-03-14 16:48 ` [PATCH V4 net-next 4/5] net: add support for sending " Andreas Roeseler
2021-03-14 16:48 ` [PATCH V4 net-next 5/5] icmp: add response to " Andreas Roeseler
2021-03-15 15:50   ` Willem de Bruijn
2021-03-15 19:09     ` Andreas Roeseler
2021-03-15 19:34       ` Willem de Bruijn
     [not found]   ` <202103150433.OwOTmI15-lkp@intel.com>
2021-03-18  3:11     ` Andreas Roeseler [this message]
2021-03-18  3:19       ` David Miller
2021-03-18  3:24         ` David Ahern
2021-03-20 16:01           ` Andreas Roeseler
2021-03-20 16:43             ` David Ahern

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=72c4ccfc219c830f1d289c3d4c8a43aec6e94877.camel@gmail.com \
    --to=andreas.a.roeseler@gmail.com \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=yoshfuji@linux-ipv6.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).