From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [ast:fexit_fix 2/2] kernel/bpf/trampoline.c:199:29: sparse: sparse: symbol 'bpf_trampoline_image_alloc' was not declared. Should it be
Date: Sat, 13 Mar 2021 11:11:59 +0800 [thread overview]
Message-ID: <202103131127.9qW7wv57-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1334 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/ast/bpf.git fexit_fix
head: d0953e3c28d70fa9d39e6db07d2cffbe7ce1f0e2
commit: d0953e3c28d70fa9d39e6db07d2cffbe7ce1f0e2 [2/2] bpf: Fix fexit trampoline.
config: x86_64-randconfig-s032-20210312 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.3-262-g5e674421-dirty
# https://git.kernel.org/pub/scm/linux/kernel/git/ast/bpf.git/commit/?id=d0953e3c28d70fa9d39e6db07d2cffbe7ce1f0e2
git remote add ast https://git.kernel.org/pub/scm/linux/kernel/git/ast/bpf.git
git fetch --no-tags ast fexit_fix
git checkout d0953e3c28d70fa9d39e6db07d2cffbe7ce1f0e2
# save the attached .config to linux build tree
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
"sparse warnings: (new ones prefixed by >>)"
>> kernel/bpf/trampoline.c:199:29: sparse: sparse: symbol 'bpf_trampoline_image_alloc' was not declared. Should it be static?
Please review and possibly fold the followup patch.
---
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: 42557 bytes --]
next reply other threads:[~2021-03-13 3:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-13 3:11 kernel test robot [this message]
2021-03-13 3:12 ` [RFC PATCH ast] bpf: bpf_trampoline_image_alloc() can be static 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=202103131127.9qW7wv57-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.