From: kernel test robot <lkp@intel.com>
To: James Morse <james.morse@arm.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Catalin Marinas <catalin.marinas@arm.com>
Subject: arch/arm64/kernel/proton-pack.c:953 this_cpu_set_vectors() warn: unsigned 'slot' is never less than zero.
Date: Sat, 26 Mar 2022 15:09:22 +0800 [thread overview]
Message-ID: <202203261509.y4KJfZNv-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 52d543b5497cf31d6baeb0bcfe5a5474c3238578
commit: 558c303c9734af5a813739cd284879227f7297d2 arm64: Mitigate spectre style branch history side channels
date: 4 weeks ago
config: arm64-randconfig-m031-20220325 (https://download.01.org/0day-ci/archive/20220326/202203261509.y4KJfZNv-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 11.2.0
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
smatch warnings:
arch/arm64/kernel/proton-pack.c:953 this_cpu_set_vectors() warn: unsigned 'slot' is never less than zero.
vim +/slot +953 arch/arm64/kernel/proton-pack.c
948
949 static void this_cpu_set_vectors(enum arm64_bp_harden_el1_vectors slot)
950 {
951 const char *v = arm64_get_bp_hardening_vector(slot);
952
> 953 if (slot < 0)
954 return;
955
956 __this_cpu_write(this_cpu_vector, v);
957
958 /*
959 * When KPTI is in use, the vectors are switched when exiting to
960 * user-space.
961 */
962 if (arm64_kernel_unmapped_at_el0())
963 return;
964
965 write_sysreg(v, vbar_el1);
966 isb();
967 }
968
--
0-DAY CI Kernel Test Service
https://01.org/lkp
next reply other threads:[~2022-03-26 7:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-26 7:09 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-01-11 17:41 arch/arm64/kernel/proton-pack.c:953 this_cpu_set_vectors() warn: unsigned 'slot' is never less than zero kernel test robot
2023-01-09 2:39 kernel test robot
2022-03-12 6:32 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=202203261509.y4KJfZNv-lkp@intel.com \
--to=lkp@intel.com \
--cc=catalin.marinas@arm.com \
--cc=james.morse@arm.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.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