All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: linux-kernel@vger.kernel.org, hpa@zytor.com,
	schwidefsky@de.ibm.com, luto@amacapital.net,
	keescook@chromium.org, linux@arm.linux.org.uk,
	ralf@linux-mips.org, heiko.carstens@de.ibm.com,
	tglx@linutronix.de
Cc: linux-tip-commits@vger.kernel.org
Subject: Re: [tip:x86/seccomp] seccomp,x86,arm,mips,s390: Remove nr parameter from secure_computing
Date: Tue, 16 Sep 2014 08:34:42 +0200	[thread overview]
Message-ID: <20140916063442.GA14807@gmail.com> (raw)
In-Reply-To: <tip-a4412fc9486ec85686c6c7929e7e829f62ae377e@git.kernel.org>


* tip-bot for Andy Lutomirski <tipbot@zytor.com> wrote:

> Commit-ID:  a4412fc9486ec85686c6c7929e7e829f62ae377e
> Gitweb:     http://git.kernel.org/tip/a4412fc9486ec85686c6c7929e7e829f62ae377e
> Author:     Andy Lutomirski <luto@amacapital.net>
> AuthorDate: Mon, 21 Jul 2014 18:49:14 -0700
> Committer:  Kees Cook <keescook@chromium.org>
> CommitDate: Wed, 3 Sep 2014 14:58:17 -0700
> 
> seccomp,x86,arm,mips,s390: Remove nr parameter from secure_computing

So, this commit in -tip, combined with Linus's latest 
(v3.17-rc5), produces this build failure or arch/parisc 
defconfig:

/home/mingo/tip/arch/parisc/kernel/ptrace.c: In function 'do_syscall_trace_enter':
/home/mingo/tip/arch/parisc/kernel/ptrace.c:274: error: implicit declaration of function 'secure_computing'
make[2]: *** [arch/parisc/kernel/ptrace.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [arch/parisc/kernel] Error 2

My guess is that the interaction was caused by:

  c90f06943e05 parisc: Wire up seccomp, getrandom and memfd_create syscalls

Thanks,

	Ingo

       reply	other threads:[~2014-09-16  6:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <tip-a4412fc9486ec85686c6c7929e7e829f62ae377e@git.kernel.org>
2014-09-16  6:34 ` Ingo Molnar [this message]
2014-09-16 22:57   ` [tip:x86/seccomp] seccomp,x86,arm,mips,s390: Remove nr parameter from secure_computing Andy Lutomirski

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=20140916063442.GA14807@gmail.com \
    --to=mingo@kernel.org \
    --cc=heiko.carstens@de.ibm.com \
    --cc=hpa@zytor.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=luto@amacapital.net \
    --cc=ralf@linux-mips.org \
    --cc=schwidefsky@de.ibm.com \
    --cc=tglx@linutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.