From: kernel test robot <lkp@intel.com>
To: Evgenii Stepanov <eugenis@google.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Peter Collingbourne <pcc@google.com>
Cc: kbuild-all@lists.01.org, Kenny Root <kroot@google.com>,
Marc Zyngier <maz@kernel.org>, Will Deacon <will@kernel.org>,
Vincenzo Frascino <vincenzo.frascino@arm.com>,
Andrey Konovalov <andreyknvl@gmail.com>,
Mark Brown <broonie@kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
Evgenii Stepanov <eugenis@google.com>
Subject: Re: [PATCH v3] arm64: mte: move register initialization to C
Date: Sun, 4 Sep 2022 21:05:59 +0800 [thread overview]
Message-ID: <202209042051.7ivKujfl-lkp@intel.com> (raw)
In-Reply-To: <20220901211954.750634-1-eugenis@google.com>
Hi Evgenii,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on arm64/for-next/core]
[also build test ERROR on linus/master v6.0-rc3 next-20220901]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Evgenii-Stepanov/arm64-mte-move-register-initialization-to-C/20220902-052059
base: https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-next/core
config: arm64-randconfig-c033-20220904 (https://download.01.org/0day-ci/archive/20220904/202209042051.7ivKujfl-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 12.1.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/intel-lab-lkp/linux/commit/23927b7e78758b39d3463ae0a79b6b1af8fdef8b
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Evgenii-Stepanov/arm64-mte-move-register-initialization-to-C/20220902-052059
git checkout 23927b7e78758b39d3463ae0a79b6b1af8fdef8b
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=arm64 SHELL=/bin/bash arch/arm64/kernel/
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
arch/arm64/kernel/suspend.c:34:13: warning: no previous prototype for 'cpu_suspend_set_dbg_restorer' [-Wmissing-prototypes]
34 | void __init cpu_suspend_set_dbg_restorer(int (*hw_bp_restore)(unsigned int))
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
arch/arm64/kernel/suspend.c: In function '__cpu_suspend_exit':
>> arch/arm64/kernel/suspend.c:46:9: error: implicit declaration of function 'mte_suspend_exit'; did you mean 'mte_suspend_enter'? [-Werror=implicit-function-declaration]
46 | mte_suspend_exit();
| ^~~~~~~~~~~~~~~~
| mte_suspend_enter
cc1: some warnings being treated as errors
vim +46 arch/arm64/kernel/suspend.c
41
42 void notrace __cpu_suspend_exit(void)
43 {
44 unsigned int cpu = smp_processor_id();
45
> 46 mte_suspend_exit();
47
48 /*
49 * We are resuming from reset with the idmap active in TTBR0_EL1.
50 * We must uninstall the idmap and restore the expected MMU
51 * state before we can possibly return to userspace.
52 */
53 cpu_uninstall_idmap();
54
55 /* Restore CnP bit in TTBR1_EL1 */
56 if (system_supports_cnp())
57 cpu_replace_ttbr1(lm_alias(swapper_pg_dir), idmap_pg_dir);
58
59 /*
60 * PSTATE was not saved over suspend/resume, re-enable any detected
61 * features that might not have been set correctly.
62 */
63 __uaccess_enable_hw_pan();
64
65 /*
66 * Restore HW breakpoint registers to sane values
67 * before debug exceptions are possibly reenabled
68 * by cpu_suspend()s local_daif_restore() call.
69 */
70 if (hw_breakpoint_restore)
71 hw_breakpoint_restore(cpu);
72
73 /*
74 * On resume, firmware implementing dynamic mitigation will
75 * have turned the mitigation on. If the user has forcefully
76 * disabled it, make sure their wishes are obeyed.
77 */
78 spectre_v4_enable_mitigation(NULL);
79
80 /* Restore additional feature-specific configuration */
81 ptrauth_suspend_exit();
82 }
83
--
0-DAY CI Kernel Test Service
https://01.org/lkp
prev parent reply other threads:[~2022-09-04 13:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 21:19 Evgenii Stepanov
2022-09-04 13:05 ` 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=202209042051.7ivKujfl-lkp@intel.com \
--to=lkp@intel.com \
--cc=andreyknvl@gmail.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=eugenis@google.com \
--cc=kbuild-all@lists.01.org \
--cc=kroot@google.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=pcc@google.com \
--cc=vincenzo.frascino@arm.com \
--cc=will@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
all inboxes | Powered by JetHome®