From: kbuild test robot <lkp@intel.com>
To: Alexander Potapenko <glider@google.com>
Cc: kbuild-all@01.org, adech.fo@gmail.com, dvyukov@google.com,
ryabinin.a.a@gmail.com, will.deacon@arm.com,
catalin.marinas@arm.com, mark.rutland@arm.com,
akpm@linux-foundation.org, kasan-dev@googlegroups.com,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v1] kasan, arm64: Unpoison dirty stack frames when resuming from suspend.
Date: Sat, 27 Feb 2016 09:05:44 +0800 [thread overview]
Message-ID: <201602270944.MOAjfHX8%fengguang.wu@intel.com> (raw)
In-Reply-To: <c08aa050cb03e40098775dc8d200f073451c342e.1456489933.git.glider@google.com>
[-- Attachment #1: Type: text/plain, Size: 2548 bytes --]
Hi Alexander,
[auto build test WARNING on arm64/for-next/core]
[also build test WARNING on v4.5-rc5 next-20160226]
[if your patch is applied to the wrong git tree, please drop us a note to help improving the system]
url: https://github.com/0day-ci/linux/commits/Alexander-Potapenko/kasan-arm64-Unpoison-dirty-stack-frames-when-resuming-from-suspend/20160226-204052
base: https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux for-next/core
config: arm64-allyesconfig (attached as .config)
reproduce:
wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
make.cross ARCH=arm64
All warnings (new ones prefixed by >>):
mm/kasan/kasan.c: In function 'kasan_stack_watermark':
>> mm/kasan/kasan.c:564:13: warning: assignment makes integer from pointer without a cast
*watermark = __builtin_frame_address(0);
^
mm/kasan/kasan.c: In function 'kasan_cpu_resume':
>> mm/kasan/kasan.c:570:21: warning: initialization makes integer from pointer without a cast
unsigned long sp = __builtin_frame_address(0);
^
>> mm/kasan/kasan.c:579:3: warning: passing argument 1 of 'kasan_unpoison_shadow' makes pointer from integer without a cast
kasan_unpoison_shadow(*watermark, sp - *watermark);
^
mm/kasan/kasan.c:53:6: note: expected 'const void *' but argument is of type 'long unsigned int'
void kasan_unpoison_shadow(const void *address, size_t size)
^
vim +564 mm/kasan/kasan.c
558 * will be used upon resume to unpoison the dirty stack frames.
559 */
560 void kasan_stack_watermark(void)
561 {
562 unsigned long *watermark = this_cpu_ptr(&cpu_stack_watermark);
563
> 564 *watermark = __builtin_frame_address(0);
565 }
566 EXPORT_SYMBOL_GPL(kasan_stack_watermark);
567
568 void kasan_cpu_resume(void)
569 {
> 570 unsigned long sp = __builtin_frame_address(0);
571 unsigned long *watermark = this_cpu_ptr(&cpu_stack_watermark);
572
573 if (*watermark == 0) {
574 WARN_ON_ONCE(*watermark == 0);
575 *watermark = sp;
576 return;
577 }
578 if (sp > *watermark) {
> 579 kasan_unpoison_shadow(*watermark, sp - *watermark);
580 *watermark = 0;
581 }
582 }
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 48245 bytes --]
prev parent reply other threads:[~2016-02-27 1:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 12:38 Alexander Potapenko
2016-02-26 13:53 ` Mark Rutland
2016-02-26 17:28 ` Alexander Potapenko
2016-03-01 19:37 ` Mark Rutland
2016-03-01 19:42 ` Mark Rutland
2016-03-01 20:05 ` [PATCH] sched/kasan: clear stale stack poison kbuild test robot
2016-03-02 12:53 ` [PATCH v1] kasan, arm64: Unpoison dirty stack frames when resuming from suspend Andrey Ryabinin
2016-03-02 13:51 ` [PATCH 1/2] cpu, idle: move init_idle() out of idle_thread_get() Andrey Ryabinin
2016-03-02 13:51 ` [PATCH 2/2] kasan: unpoison stack of idle task on cpu online Andrey Ryabinin
2016-03-02 14:50 ` Mark Rutland
2016-03-02 15:27 ` Andrey Ryabinin
2016-03-02 15:43 ` Mark Rutland
2016-02-27 1:05 ` kbuild 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=201602270944.MOAjfHX8%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=adech.fo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=kbuild-all@01.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=ryabinin.a.a@gmail.com \
--cc=will.deacon@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
all inboxes | Powered by JetHome®