From: kernel test robot <lkp@intel.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Hannes Reinecke <hare@suse.de>
Subject: [cel:topic-rpc-with-tls-upcall 3/19] af_tlsh.c:undefined reference to `inet6_getname'
Date: Sun, 22 May 2022 08:17:45 +0800 [thread overview]
Message-ID: <202205220836.G9R3wOR1-lkp@intel.com> (raw)
tree: git://git.kernel.org/pub/scm/linux/kernel/git/cel/linux topic-rpc-with-tls-upcall
head: c484b8917f3569f6fdf4026936f9452dbeb1a8c3
commit: 633fdf59349bcca5ca23885959506d643bbb9daf [3/19] net/tls: Add support for PF_TLSH (a TLS handshake listener)
config: i386-randconfig-a005 (https://download.01.org/0day-ci/archive/20220522/202205220836.G9R3wOR1-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-1) 11.3.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/cel/linux.git/commit/?id=633fdf59349bcca5ca23885959506d643bbb9daf
git remote add cel git://git.kernel.org/pub/scm/linux/kernel/git/cel/linux
git fetch --no-tags cel topic-rpc-with-tls-upcall
git checkout 633fdf59349bcca5ca23885959506d643bbb9daf
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
ld: net/tls/af_tlsh.o: in function `tlsh_getname':
>> af_tlsh.c:(.text+0x1f7): undefined reference to `inet6_getname'
ld: net/tls/af_tlsh.o: in function `tlsh_release':
>> af_tlsh.c:(.text+0x12f7): undefined reference to `inet6_release'
--
0-DAY CI Kernel Test Service
https://01.org/lkp
next reply other threads:[~2022-05-22 0:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-22 0:17 kernel test robot [this message]
2022-05-30 0:42 [cel:topic-rpc-with-tls-upcall 3/19] af_tlsh.c:undefined reference to `inet6_getname' 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=202205220836.G9R3wOR1-lkp@intel.com \
--to=lkp@intel.com \
--cc=chuck.lever@oracle.com \
--cc=hare@suse.de \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@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).