From: kernel test robot <lkp@intel.com>
To: Jiang Wang <jiang.wang@bytedance.com>, netdev@vger.kernel.org
Cc: kbuild-all@lists.01.org, cong.wang@bytedance.com,
duanxiongchun@bytedance.com, xieyongji@bytedance.com,
chaiwen.cc@bytedance.com, Jakub Kicinski <kuba@kernel.org>,
John Fastabend <john.fastabend@gmail.com>,
Daniel Borkmann <daniel@iogearbox.net>,
Jakub Sitnicki <jakub@cloudflare.com>,
Lorenz Bauer <lmb@cloudflare.com>
Subject: Re: [PATCH bpf-next v6 2/5] af_unix: add unix_stream_proto for sockmap
Date: Sun, 15 Aug 2021 11:55:08 +0800 [thread overview]
Message-ID: <202108151123.JoQjrtLu-lkp@intel.com> (raw)
In-Reply-To: <20210814042754.3351268-3-jiang.wang@bytedance.com>
[-- Attachment #1: Type: text/plain, Size: 1409 bytes --]
Hi Jiang,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on bpf-next/master]
url: https://github.com/0day-ci/linux/commits/Jiang-Wang/sockmap-add-sockmap-support-for-unix-stream-socket/20210814-123038
base: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git master
config: mips-allmodconfig (attached as .config)
compiler: mips-linux-gcc (GCC) 11.2.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/94e7d17a013ee7fdeb46f5d790f066841eec6459
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Jiang-Wang/sockmap-add-sockmap-support-for-unix-stream-socket/20210814-123038
git checkout 94e7d17a013ee7fdeb46f5d790f066841eec6459
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.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 >>, old ones prefixed by <<):
>> ERROR: modpost: "sock_map_unhash" [net/unix/unix.ko] undefined!
---
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: 70863 bytes --]
next prev parent reply other threads:[~2021-08-15 3:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-14 4:27 [PATCH bpf-next v6 0/5] sockmap: add sockmap support for unix stream socket Jiang Wang
2021-08-14 4:27 ` [PATCH bpf-next v6 1/5] af_unix: add read_sock for stream socket types Jiang Wang
2021-08-14 4:27 ` [PATCH bpf-next v6 2/5] af_unix: add unix_stream_proto for sockmap Jiang Wang
2021-08-15 3:55 ` kernel test robot [this message]
2021-08-14 4:27 ` [PATCH bpf-next v6 3/5] selftest/bpf: add tests for sockmap with unix stream type Jiang Wang
2021-08-14 4:27 ` [PATCH bpf-next v6 4/5] selftest/bpf: change udp to inet in some function names Jiang Wang
2021-08-14 4:27 ` [PATCH bpf-next v6 5/5] selftest/bpf: add new tests in sockmap for unix stream to tcp Jiang Wang
-- strict thread matches above, loose matches on Subject: below --
2021-08-09 19:47 [PATCH bpf-next v6 0/5] sockmap: add sockmap support for unix stream socket Jiang Wang
2021-08-09 19:47 ` [PATCH bpf-next v6 2/5] af_unix: add unix_stream_proto for sockmap Jiang Wang
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=202108151123.JoQjrtLu-lkp@intel.com \
--to=lkp@intel.com \
--cc=chaiwen.cc@bytedance.com \
--cc=cong.wang@bytedance.com \
--cc=daniel@iogearbox.net \
--cc=duanxiongchun@bytedance.com \
--cc=jakub@cloudflare.com \
--cc=jiang.wang@bytedance.com \
--cc=john.fastabend@gmail.com \
--cc=kbuild-all@lists.01.org \
--cc=kuba@kernel.org \
--cc=lmb@cloudflare.com \
--cc=netdev@vger.kernel.org \
--cc=xieyongji@bytedance.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).