public inbox for kernel-hardening@lists.openwall.com
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Laura Abbott <labbott@fedoraproject.org>
Cc: kbuild-all@01.org, Andrew Morton <akpm@linux-foundation.org>,
	"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
	Vlastimil Babka <vbabka@suse.cz>, Michal Hocko <mhocko@suse.com>,
	Kees Cook <keescook@chromium.org>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	kernel-hardening@lists.openwall.com
Subject: [kernel-hardening] Re: [PATCHv4 1/2] mm/page_poison.c: Enable PAGE_POISONING as a separate option
Date: Sat, 5 Mar 2016 08:17:32 +0800	[thread overview]
Message-ID: <201603050834.dtgWC134%fengguang.wu@intel.com> (raw)
In-Reply-To: <1457135448-15541-2-git-send-email-labbott@fedoraproject.org>

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

Hi Laura,

[auto build test ERROR on v4.5-rc6]
[cannot apply to next-20160304]
[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/Laura-Abbott/mm-page_poison-c-Enable-PAGE_POISONING-as-a-separate-option/20160305-075416
config: sparc64-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=sparc64 

All errors (new ones prefixed by >>):

   mm/page_poison.c: In function 'init_page_poisoning':
>> mm/page_poison.c:43:3: error: implicit declaration of function 'debug_pagealloc_enabled' [-Werror=implicit-function-declaration]
      if (!want_page_poisoning && !debug_pagealloc_enabled())
      ^
   cc1: some warnings being treated as errors

vim +/debug_pagealloc_enabled +43 mm/page_poison.c

    37	{
    38		/*
    39		 * page poisoning is debug page alloc for some arches. If either
    40		 * of those options are enabled, enable poisoning
    41		 */
    42		if (!IS_ENABLED(CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC)) {
  > 43			if (!want_page_poisoning && !debug_pagealloc_enabled())
    44				return;
    45		} else {
    46			if (!want_page_poisoning)

---
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: 45113 bytes --]

  reply	other threads:[~2016-03-05  0:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-04 23:50 [kernel-hardening] [PATCHv4 0/2] Sanitization of buddy pages Laura Abbott
2016-03-04 23:50 ` [kernel-hardening] [PATCHv4 1/2] mm/page_poison.c: Enable PAGE_POISONING as a separate option Laura Abbott
2016-03-05  0:17   ` kbuild test robot [this message]
2016-03-04 23:50 ` [kernel-hardening] [PATCHv4 2/2] mm/page_poisoning.c: Allow for zero poisoning Laura Abbott
2016-03-05  0:07   ` [kernel-hardening] " Andrew Morton
2016-03-08  0:33     ` Laura Abbott
2016-03-09 21:00 ` [kernel-hardening] Re: [PATCHv4 0/2] Sanitization of buddy pages Kees Cook

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=201603050834.dtgWC134%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=kbuild-all@01.org \
    --cc=keescook@chromium.org \
    --cc=kernel-hardening@lists.openwall.com \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=labbott@fedoraproject.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.com \
    --cc=vbabka@suse.cz \
    /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