mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: kbuild-all@01.org, Andrey Ryabinin <aryabinin@virtuozzo.com>,
	Alexander Potapenko <glider@google.com>,
	Dmitry Vyukov <dvyukov@google.com>,
	linux-kernel@vger.kernel.org,
	Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH] kasan: Respect /proc/sys/kernel/traceoff_on_warning
Date: Wed, 25 Jan 2017 23:29:28 +0800	[thread overview]
Message-ID: <201701252339.kQ84CDiQ%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170125142524.GQ6515@twins.programming.kicks-ass.net>

[-- Attachment #1: Type: text/plain, Size: 1381 bytes --]

Hi Peter,

[auto build test ERROR on mmotm/master]
[also build test ERROR on v4.10-rc5 next-20170125]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]

url:    https://github.com/0day-ci/linux/commits/Peter-Zijlstra/kasan-Respect-proc-sys-kernel-traceoff_on_warning/20170125-230535
base:   git://git.cmpxchg.org/linux-mmotm.git master
config: x86_64-randconfig-x008-201704 (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
        # save the attached .config to linux build tree
        make ARCH=x86_64 

All errors (new ones prefixed by >>):

   mm/kasan/report.c: In function 'kasan_report':
>> mm/kasan/report.c:303:2: error: implicit declaration of function 'disable_trace_on_warning' [-Werror=implicit-function-declaration]
     disable_trace_on_warning();
     ^~~~~~~~~~~~~~~~~~~~~~~~
   cc1: some warnings being treated as errors

vim +/disable_trace_on_warning +303 mm/kasan/report.c

   297	{
   298		struct kasan_access_info info;
   299	
   300		if (likely(!kasan_report_enabled()))
   301			return;
   302	
 > 303		disable_trace_on_warning();
   304	
   305		info.access_addr = (void *)addr;
   306		info.access_size = size;

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 27451 bytes --]

  parent reply	other threads:[~2017-01-25 15:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-25 14:25 Peter Zijlstra
2017-01-25 14:28 ` Peter Zijlstra
2017-01-25 14:32   ` Alexander Potapenko
2017-01-25 14:35     ` Peter Zijlstra
2017-01-25 14:37       ` Alexander Potapenko
2017-01-30 19:18       ` Steven Rostedt
2017-01-25 14:38 ` Alexander Potapenko
2017-01-25 15:29 ` kbuild test robot [this message]
2017-01-25 16:41 ` [PATCH v2] " Andrey Ryabinin

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=201701252339.kQ84CDiQ%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=aryabinin@virtuozzo.com \
    --cc=dvyukov@google.com \
    --cc=glider@google.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.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®