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,
"Andy Chiu" <andy.chiu@sifive.com>
Cc: oe-kbuild-all@lists.linux.dev, "Björn Töpel" <bjorn@rivosinc.com>,
linux-kernel@vger.kernel.org, linux@rivosinc.com,
"Rémi Denis-Courmont" <remi@remlab.net>,
"Darius Rad" <darius@bluespec.com>
Subject: Re: [PATCH v3] riscv: Discard vector state on syscalls
Date: Thu, 29 Jun 2023 20:25:31 +0800 [thread overview]
Message-ID: <202306292011.OGfLGBam-lkp@intel.com> (raw)
In-Reply-To: <20230629062730.985184-1-bjorn@kernel.org>
Hi Björn,
kernel test robot noticed the following build errors:
[auto build test ERROR on 488833ccdcac118da16701f4ee0673b20ba47fe3]
url: https://github.com/intel-lab-lkp/linux/commits/Bj-rn-T-pel/riscv-Discard-vector-state-on-syscalls/20230629-142852
base: 488833ccdcac118da16701f4ee0673b20ba47fe3
patch link: https://lore.kernel.org/r/20230629062730.985184-1-bjorn%40kernel.org
patch subject: [PATCH v3] riscv: Discard vector state on syscalls
config: riscv-allnoconfig (https://download.01.org/0day-ci/archive/20230629/202306292011.OGfLGBam-lkp@intel.com/config)
compiler: riscv64-linux-gcc (GCC) 12.3.0
reproduce: (https://download.01.org/0day-ci/archive/20230629/202306292011.OGfLGBam-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/202306292011.OGfLGBam-lkp@intel.com/
All errors (new ones prefixed by >>):
arch/riscv/kernel/traps.c: In function 'do_trap_ecall_u':
>> arch/riscv/kernel/traps.c:299:17: error: implicit declaration of function 'riscv_v_vstate_discard'; did you mean 'riscv_v_vstate_restore'? [-Werror=implicit-function-declaration]
299 | riscv_v_vstate_discard(regs);
| ^~~~~~~~~~~~~~~~~~~~~~
| riscv_v_vstate_restore
cc1: some warnings being treated as errors
vim +299 arch/riscv/kernel/traps.c
290
291 asmlinkage __visible __trap_section void do_trap_ecall_u(struct pt_regs *regs)
292 {
293 if (user_mode(regs)) {
294 ulong syscall = regs->a7;
295
296 regs->epc += 4;
297 regs->orig_a0 = regs->a0;
298
> 299 riscv_v_vstate_discard(regs);
300
301 syscall = syscall_enter_from_user_mode(regs, syscall);
302
303 if (syscall < NR_syscalls)
304 syscall_handler(regs, syscall);
305 else
306 regs->a0 = -ENOSYS;
307
308 syscall_exit_to_user_mode(regs);
309 } else {
310 irqentry_state_t state = irqentry_nmi_enter(regs);
311
312 do_trap_error(regs, SIGILL, ILL_ILLTRP, regs->epc,
313 "Oops - environment call from U-mode");
314
315 irqentry_nmi_exit(regs, state);
316 }
317
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2023-06-29 12:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-29 6:27 [PATCH v3] riscv: Discard vector state on syscalls Björn Töpel
2023-06-29 7:16 ` Conor Dooley
2023-06-29 13:48 ` Björn Töpel
2023-06-29 8:04 ` kernel test robot
2023-06-29 12:25 ` kernel test robot [this message]
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=202306292011.OGfLGBam-lkp@intel.com \
--to=lkp@intel.com \
--cc=andy.chiu@sifive.com \
--cc=aou@eecs.berkeley.edu \
--cc=bjorn@kernel.org \
--cc=bjorn@rivosinc.com \
--cc=darius@bluespec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux@rivosinc.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=remi@remlab.net \
/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