From: kernel test robot <lkp@intel.com>
To: Menglong Dong <menglong8.dong@gmail.com>,
rostedt@goodmis.org, mark.rutland@arm.com,
alexei.starovoitov@gmail.com
Cc: oe-kbuild-all@lists.linux.dev, catalin.marinas@arm.com,
will@kernel.org, mhiramat@kernel.org, tglx@linutronix.de,
mingo@redhat.com, bp@alien8.de, dave.hansen@linux.intel.com,
x86@kernel.org, hpa@zytor.com, mathieu.desnoyers@efficios.com,
nathan@kernel.org, ndesaulniers@google.com, morbo@google.com,
justinstitt@google.com, dongml2@chinatelecom.cn,
akpm@linux-foundation.org, rppt@kernel.org, graf@amazon.com,
dan.j.williams@intel.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
bpf@vger.kernel.org, llvm@lists.linux.dev
Subject: Re: [PATCH bpf-next v2] add function metadata support
Date: Fri, 28 Feb 2025 00:32:28 +0800 [thread overview]
Message-ID: <202502280004.QmU2zIb5-lkp@intel.com> (raw)
In-Reply-To: <20250226121537.752241-1-dongml2@chinatelecom.cn>
Hi Menglong,
kernel test robot noticed the following build warnings:
[auto build test WARNING on bpf-next/master]
url: https://github.com/intel-lab-lkp/linux/commits/Menglong-Dong/add-function-metadata-support/20250226-202312
base: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git master
patch link: https://lore.kernel.org/r/20250226121537.752241-1-dongml2%40chinatelecom.cn
patch subject: [PATCH bpf-next v2] add function metadata support
config: x86_64-randconfig-r112-20250227 (https://download.01.org/0day-ci/archive/20250228/202502280004.QmU2zIb5-lkp@intel.com/config)
compiler: clang version 19.1.7 (https://github.com/llvm/llvm-project cd708029e0b2869e80abe31ddb175f7c35361f90)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250228/202502280004.QmU2zIb5-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/202502280004.QmU2zIb5-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
kernel/trace/kfunc_md.c:12:23: sparse: sparse: symbol 'kfunc_mds' redeclared with different type (different address spaces):
kernel/trace/kfunc_md.c:12:23: sparse: struct kfunc_md [noderef] __rcu *[addressable] [toplevel] kfunc_mds
kernel/trace/kfunc_md.c: note: in included file:
include/linux/kfunc_md.h:16:24: sparse: note: previously declared as:
include/linux/kfunc_md.h:16:24: sparse: struct kfunc_md *extern [addressable] [toplevel] kfunc_mds
>> kernel/trace/kfunc_md.c:186:20: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct kfunc_md *md @@ got struct kfunc_md [noderef] __rcu * @@
kernel/trace/kfunc_md.c:186:20: sparse: expected struct kfunc_md *md
kernel/trace/kfunc_md.c:186:20: sparse: got struct kfunc_md [noderef] __rcu *
vim +186 kernel/trace/kfunc_md.c
169
170 /* Get a exist metadata by the function address, and NULL will be returned
171 * if not exist.
172 *
173 * NOTE: rcu lock should be held during reading the metadata, and
174 * kfunc_md_lock should be held if writing happens.
175 */
176 struct kfunc_md *kfunc_md_find(void *ip)
177 {
178 struct kfunc_md *md;
179 u32 index;
180
181 if (kfunc_md_arch_exist(ip)) {
182 index = kfunc_md_get_index(ip);
183 if (WARN_ON_ONCE(index >= kfunc_md_count))
184 return NULL;
185
> 186 md = &kfunc_mds[index];
187 return md;
188 }
189 return NULL;
190 }
191 EXPORT_SYMBOL_GPL(kfunc_md_find);
192
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-02-27 16:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-26 12:15 [PATCH bpf-next v2] add function metadata support Menglong Dong
2025-02-27 15:18 ` kernel test robot
2025-02-27 16:32 ` kernel test robot [this message]
2025-02-27 16:53 ` Peter Zijlstra
2025-02-28 9:53 ` Menglong Dong
2025-02-28 10:26 ` Peter Zijlstra
2025-02-28 10:29 ` Peter Zijlstra
2025-02-28 13:01 ` Menglong Dong
2025-02-27 17:48 ` kernel test robot
2025-02-28 0:43 ` kernel test robot
2025-03-04 6:25 ` 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=202502280004.QmU2zIb5-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=alexei.starovoitov@gmail.com \
--cc=bp@alien8.de \
--cc=bpf@vger.kernel.org \
--cc=catalin.marinas@arm.com \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=dongml2@chinatelecom.cn \
--cc=graf@amazon.com \
--cc=hpa@zytor.com \
--cc=justinstitt@google.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mark.rutland@arm.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=menglong8.dong@gmail.com \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rostedt@goodmis.org \
--cc=rppt@kernel.org \
--cc=tglx@linutronix.de \
--cc=will@kernel.org \
--cc=x86@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).