From: kernel test robot <lkp@intel.com>
To: kernel@openeuler.org, JofDiamonds <kwb0523@163.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [openeuler:OLK-5.10 21426/30000] net/core/sock_map.c:1501:5: sparse: sparse: symbol 'sock_map_prog_lookup' was not declared. Should it be static?
Date: Sun, 17 Mar 2024 17:47:20 +0800 [thread overview]
Message-ID: <202403171747.MBuYnaps-lkp@intel.com> (raw)
tree: https://gitee.com/openeuler/kernel.git OLK-5.10
head: 32bb7b0a7c87769858fbb9d60574b830383c28f7
commit: 050383882de382969e4fb8362235749b232cccae [21426/30000] bpf: support BPF_PROG_QUERY for progs attached to sockmap
config: x86_64-randconfig-123-20240317 (https://download.01.org/0day-ci/archive/20240317/202403171747.MBuYnaps-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240317/202403171747.MBuYnaps-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202403171747.MBuYnaps-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> net/core/sock_map.c:1501:5: sparse: sparse: symbol 'sock_map_prog_lookup' was not declared. Should it be static?
vim +/sock_map_prog_lookup +1501 net/core/sock_map.c
1500
> 1501 int sock_map_prog_lookup(struct bpf_map *map, struct bpf_prog ***pprog,
1502 u32 which)
1503 {
1504 struct sk_psock_progs *progs = sock_map_progs(map);
1505
1506 if (!progs)
1507 return -EOPNOTSUPP;
1508
1509 switch (which) {
1510 case BPF_SK_MSG_VERDICT:
1511 *pprog = &progs->msg_parser;
1512 break;
1513 case BPF_SK_SKB_STREAM_PARSER:
1514 *pprog = &progs->skb_parser;
1515 break;
1516 case BPF_SK_SKB_STREAM_VERDICT:
1517 *pprog = &progs->skb_verdict;
1518 break;
1519 default:
1520 return -EOPNOTSUPP;
1521 }
1522 return 0;
1523 }
1524
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-03-17 9:48 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=202403171747.MBuYnaps-lkp@intel.com \
--to=lkp@intel.com \
--cc=kernel@openeuler.org \
--cc=kwb0523@163.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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.