From: kernel test robot <lkp@intel.com>
To: Peter Collingbourne <pcc@google.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Vincenzo Frascino <vincenzo.frascino@arm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Andrey Konovalov <andreyknvl@gmail.com>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Peter Collingbourne <pcc@google.com>,
linux-arm-kernel@lists.infradead.org, kasan-dev@googlegroups.com
Subject: Re: [PATCH] kasan: also display registers for reports from HW exceptions
Date: Sat, 10 Sep 2022 17:29:25 +0800 [thread overview]
Message-ID: <202209101733.SvgcwWsA-lkp@intel.com> (raw)
In-Reply-To: <20220910052426.943376-1-pcc@google.com>
Hi Peter,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on next-20220909]
[cannot apply to arm64/for-next/core linus/master v6.0-rc4 v6.0-rc3 v6.0-rc2 v6.0-rc4]
[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/Peter-Collingbourne/kasan-also-display-registers-for-reports-from-HW-exceptions/20220910-132721
base: 9a82ccda91ed2b40619cb3c10d446ae1f97bab6e
config: powerpc-allmodconfig (https://download.01.org/0day-ci/archive/20220910/202209101733.SvgcwWsA-lkp@intel.com/config)
compiler: powerpc-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/2140392d32582f62b922eaf4d1824e5a7838b420
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Peter-Collingbourne/kasan-also-display-registers-for-reports-from-HW-exceptions/20220910-132721
git checkout 2140392d32582f62b922eaf4d1824e5a7838b420
# 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=powerpc SHELL=/bin/bash
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> mm/kasan/report.c:506:6: warning: no previous prototype for 'kasan_report_regs' [-Wmissing-prototypes]
506 | bool kasan_report_regs(unsigned long addr, size_t size, bool is_write,
| ^~~~~~~~~~~~~~~~~
vim +/kasan_report_regs +506 mm/kasan/report.c
505
> 506 bool kasan_report_regs(unsigned long addr, size_t size, bool is_write,
507 struct pt_regs *regs)
508 {
509 return __kasan_report(addr, size, is_write, instruction_pointer(regs),
510 regs);
511 }
512
--
0-DAY CI Kernel Test Service
https://01.org/lkp
next prev parent reply other threads:[~2022-09-10 9:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-10 5:24 Peter Collingbourne
2022-09-10 9:29 ` kernel test robot [this message]
2022-09-10 9:29 ` kernel test robot
2022-09-10 21:40 ` Andrey Konovalov
2022-09-13 4:00 ` Peter Collingbourne
2022-09-24 18:23 ` Andrey Konovalov
2022-09-27 1:21 ` Peter Collingbourne
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=202209101733.SvgcwWsA-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=kasan-dev@googlegroups.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mm@kvack.org \
--cc=pcc@google.com \
--cc=vincenzo.frascino@arm.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