From: kernel test robot <lkp@intel.com>
To: "Björn Töpel" <bjorn@kernel.org>,
"Paul Walmsley" <paul.walmsley@sifive.com>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Albert Ou" <aou@eecs.berkeley.edu>,
linux-riscv@lists.infradead.org, "Guo Ren" <guoren@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
"Björn Töpel" <bjorn@rivosinc.com>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
"Nam Cao" <namcaov@gmail.com>
Subject: Re: [PATCH] riscv: Only consider swbp/ss handlers for correct privileged mode
Date: Sun, 27 Aug 2023 18:46:48 +0800 [thread overview]
Message-ID: <202308271841.HlnnHFL7-lkp@intel.com> (raw)
In-Reply-To: <20230827083949.204927-1-bjorn@kernel.org>
Hi Björn,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 7d2f353b2682dcfe5f9bc71e5b61d5b61770d98e]
url: https://github.com/intel-lab-lkp/linux/commits/Bj-rn-T-pel/riscv-Only-consider-swbp-ss-handlers-for-correct-privileged-mode/20230827-164313
base: 7d2f353b2682dcfe5f9bc71e5b61d5b61770d98e
patch link: https://lore.kernel.org/r/20230827083949.204927-1-bjorn%40kernel.org
patch subject: [PATCH] riscv: Only consider swbp/ss handlers for correct privileged mode
config: riscv-randconfig-001-20230827 (https://download.01.org/0day-ci/archive/20230827/202308271841.HlnnHFL7-lkp@intel.com/config)
compiler: clang version 17.0.0 (https://github.com/llvm/llvm-project.git 4a5ac14ee968ff0ad5d2cc1ffa0299048db4c88a)
reproduce: (https://download.01.org/0day-ci/archive/20230827/202308271841.HlnnHFL7-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/202308271841.HlnnHFL7-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from kernel/sched/core.c:49:
In file included from include/linux/kprobes.h:32:
>> arch/riscv/include/asm/kprobes.h:44:62: warning: omitting the parameter name in a function definition is a C2x extension [-Wc2x-extensions]
44 | static inline bool kprobe_breakpoint_handler(struct pt_regs *)
| ^
arch/riscv/include/asm/kprobes.h:49:63: warning: omitting the parameter name in a function definition is a C2x extension [-Wc2x-extensions]
49 | static inline bool kprobe_single_step_handler(struct pt_regs *)
| ^
kernel/sched/core.c:3695:20: warning: unused function 'rq_has_pinned_tasks' [-Wunused-function]
3695 | static inline bool rq_has_pinned_tasks(struct rq *rq)
| ^
kernel/sched/core.c:5821:20: warning: unused function 'sched_tick_start' [-Wunused-function]
5821 | static inline void sched_tick_start(int cpu) { }
| ^
kernel/sched/core.c:5822:20: warning: unused function 'sched_tick_stop' [-Wunused-function]
5822 | static inline void sched_tick_stop(int cpu) { }
| ^
kernel/sched/core.c:6522:20: warning: unused function 'sched_core_cpu_starting' [-Wunused-function]
6522 | static inline void sched_core_cpu_starting(unsigned int cpu) {}
| ^
kernel/sched/core.c:6523:20: warning: unused function 'sched_core_cpu_deactivate' [-Wunused-function]
6523 | static inline void sched_core_cpu_deactivate(unsigned int cpu) {}
| ^
kernel/sched/core.c:6524:20: warning: unused function 'sched_core_cpu_dying' [-Wunused-function]
6524 | static inline void sched_core_cpu_dying(unsigned int cpu) {}
| ^
8 warnings generated.
vim +44 arch/riscv/include/asm/kprobes.h
38
39 void arch_remove_kprobe(struct kprobe *p);
40 int kprobe_fault_handler(struct pt_regs *regs, unsigned int trapnr);
41 bool kprobe_breakpoint_handler(struct pt_regs *regs);
42 bool kprobe_single_step_handler(struct pt_regs *regs);
43 #else
> 44 static inline bool kprobe_breakpoint_handler(struct pt_regs *)
45 {
46 return false;
47 }
48
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
parent reply other threads:[~2023-08-27 10:46 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20230827083949.204927-1-bjorn@kernel.org>]
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=202308271841.HlnnHFL7-lkp@intel.com \
--to=lkp@intel.com \
--cc=aou@eecs.berkeley.edu \
--cc=bjorn@kernel.org \
--cc=bjorn@rivosinc.com \
--cc=guoren@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=namcaov@gmail.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.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).