mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Scott Bauer <sbauer@eng.utah.edu>
Cc: kbuild-all@01.org, sbauer@eng.utah.edu,
	linux-kernel@vger.kernel.org,
	kernel-hardening@lists.openwall.com, x86@kernel.org,
	wmealing@redhat.com, ak@linux.intel.com, luto@amacapital.net,
	Abhiram Balasubramanian <abhiram@cs.utah.edu>
Subject: Re: [PATCH v3 1/3] SROP Mitigation: Architecture independent code for signal cookies
Date: Wed, 9 Mar 2016 05:04:47 +0800	[thread overview]
Message-ID: <201603090547.9tA5klyR%fengguang.wu@intel.com> (raw)
In-Reply-To: <1457470075-4586-1-git-send-email-sbauer@eng.utah.edu>

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

Hi Scott,

[auto build test ERROR on tip/x86/core]
[also build test ERROR on v4.5-rc7]
[cannot apply to next-20160308]
[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/Scott-Bauer/SROP-Mitigation-Architecture-independent-code-for-signal-cookies/20160309-045202
config: i386-tinyconfig (attached as .config)
reproduce:
        # save the attached .config to linux build tree
        make ARCH=i386 

Note: the linux-review/Scott-Bauer/SROP-Mitigation-Architecture-independent-code-for-signal-cookies/20160309-045202 HEAD 52ff6d1c09bbf7b33f786ccaa3de5521002a92fa builds fine.
      It only hurts bisectibility.

All errors (new ones prefixed by >>):

   kernel/signal.c: In function 'verify_clear_sigcookie':
>> kernel/signal.c:2469:1: error: expected ';' before '}' token
    }
    ^

vim +2469 kernel/signal.c

  2463			return 1;
  2464	
  2465		}
  2466	
  2467		user_cookie = 0;
  2468		return put_user(user_cookie, sig_cookie_ptr)
> 2469	}
  2470	
  2471	EXPORT_SYMBOL(verify_clear_sigcookie);
  2472	EXPORT_SYMBOL(set_sigcookie);

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

  parent reply	other threads:[~2016-03-08 21:05 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-08 20:47 Scott Bauer
2016-03-08 20:47 ` [PATCH v3 2/3] x86: SROP mitigation: implement " Scott Bauer
2016-03-08 21:03   ` One Thousand Gnomes
2016-03-08 21:38     ` Scotty Bauer
2016-03-08 20:47 ` [PATCH v3 3/3] SROP mitigation: Add sysctl to disable SROP protection Scott Bauer
2016-03-08 21:00   ` One Thousand Gnomes
2016-03-10  6:36     ` [kernel-hardening] " Kees Cook
2016-03-10  6:46       ` Andy Lutomirski
2016-03-08 20:58 ` [PATCH v3 1/3] SROP Mitigation: Architecture independent code for signal cookies Andy Lutomirski
2016-03-08 21:49   ` Scotty Bauer
2016-03-08 21:57     ` Andy Lutomirski
2016-03-08 22:06       ` Scotty Bauer
2016-03-09 22:02       ` Scotty Bauer
2016-03-08 21:04 ` kbuild test robot [this message]
2016-03-09  8:32 ` Ingo Molnar
2016-03-09 22:07   ` Scotty Bauer
2016-03-09 22:22     ` Jonathan Corbet
2016-03-10  9:43       ` Ingo Molnar

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=201603090547.9tA5klyR%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=abhiram@cs.utah.edu \
    --cc=ak@linux.intel.com \
    --cc=kbuild-all@01.org \
    --cc=kernel-hardening@lists.openwall.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=sbauer@eng.utah.edu \
    --cc=wmealing@redhat.com \
    --cc=x86@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®