From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [congwang:sockmap3 2/9] net/unix/unix_bpf.c:15:17: error: 'sock_map_close' undeclared; did you mean 'sk_msg_clone'?
Date: Tue, 20 Apr 2021 03:21:17 +0800 [thread overview]
Message-ID: <202104200307.7SrsyEPk-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1847 bytes --]
tree: https://github.com/congwang/linux.git sockmap3
head: 5128e99b2a4b0d084ecb739e2108dcd2e68b11d7
commit: dedf0418fa1e61fd2d331e69e4bb936e00c614a6 [2/9] af_unix: implement ->psock_update_sk_prot()
config: alpha-randconfig-m031-20210419 (attached as .config)
compiler: alpha-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/congwang/linux/commit/dedf0418fa1e61fd2d331e69e4bb936e00c614a6
git remote add congwang https://github.com/congwang/linux.git
git fetch --no-tags congwang sockmap3
git checkout dedf0418fa1e61fd2d331e69e4bb936e00c614a6
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross W=1 ARCH=alpha
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 >>):
net/unix/unix_bpf.c: In function 'unix_bpf_rebuild_protos':
>> net/unix/unix_bpf.c:15:17: error: 'sock_map_close' undeclared (first use in this function); did you mean 'sk_msg_clone'?
15 | prot->close = sock_map_close;
| ^~~~~~~~~~~~~~
| sk_msg_clone
net/unix/unix_bpf.c:15:17: note: each undeclared identifier is reported only once for each function it appears in
vim +15 net/unix/unix_bpf.c
11
12 static void unix_bpf_rebuild_protos(struct proto *prot, const struct proto *base)
13 {
14 *prot = *base;
> 15 prot->close = sock_map_close;
16 }
17
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 33417 bytes --]
reply other threads:[~2021-04-19 19:21 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=202104200307.7SrsyEPk-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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.