All of lore.kernel.org
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: Guenter Roeck <linux@roeck-us.net>,
	Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Ingo Molnar <mingo@kernel.org>
Subject: Re: linux-next: Tree for Sep 19
Date: Sun, 21 Sep 2014 21:43:46 +0200	[thread overview]
Message-ID: <541F2A72.8030007@gmx.de> (raw)
In-Reply-To: <541DEB33.2070508@roeck-us.net>

Hi Günter,

On 09/20/2014 11:01 PM, Guenter Roeck wrote:
> On 09/20/2014 12:36 PM, Helge Deller wrote:
>> Hi Günter,
>>
>> On 09/19/2014 09:15 PM, Guenter Roeck wrote:
>>> On Fri, Sep 19, 2014 at 04:58:17PM +1000, Stephen Rothwell wrote:
>>>> Changes since 20140917:
>>>>
>>>> The fsl tree still had its build failure so I used the version from
>>>> next-20140917.
>>>>
>>>> The v4l-dvb tree lost its build failure.
>>>>
>>>> The security tree gained a conflict against the file-locks tree.
>>>>
>>>> Non-merge commits (relative to Linus' tree): 6014
>>>>   5488 files changed, 217522 insertions(+), 129375 deletions(-)
>>>>
>>>> ----------------------------------------------------------------------------
>>>>
>>>
>>> parisc:defconfig, parisc:generic-32bit_defconfig:
>>>
>>> --------------
>>> Error log:
>>> arch/parisc/kernel/ptrace.c: In function 'do_syscall_trace_enter':
>>> arch/parisc/kernel/ptrace.c:274:2: error: implicit declaration of function
>>> 'secure_computing' [-Werror=implicit-function-declaration]
>>> cc1: some warnings being treated as errors
>>> make[1]: *** [arch/parisc/kernel/ptrace.o] Error 1
>>>
>>> Bisect points to commit 273299fb6380 ('Merge branch 'x86/seccomp') which
>>> obviously doesn't help much. Suspected culprit is c90f06943e05 ('parisc: Wire up
>>> seccomp, getrandom and memfd_create syscalls') which seems to be missing an
>>> include file.
>
>> I've added this patch to my for-next tree:
>> http://git.kernel.org/cgit/linux/kernel/git/deller/parisc-linux.git/commit/?h=for-next&id=0f18557b017b3469e1f8edf5cf34c1cba856fdbe
>
> That doesn't solve the problem for me, most likely because
> HAVE_ARCH_SECCOMP_FILTER is not set for parisc in next-20140919.
> This is what seccomp.h does with it:
>
> #ifdef CONFIG_HAVE_ARCH_SECCOMP_FILTER
> static inline int secure_computing(void) { return 0; }
> #else
> static inline void secure_computing_strict(int this_syscall) { return; }
> #endif
>
> You don't have this flag in your tree. It was introduced in -next with
> commit 'seccomp,x86,arm,mips,s390: Remove nr parameter from secure_computing'.

Thanks for the hint!
Since parisc currently only supports the strict mode, I've changed the code
to call secure_computing_strict() instead of secure_computing() with this commit in my for-next tree:
http://git.kernel.org/cgit/linux/kernel/git/deller/parisc-linux.git/commit/?h=for-next&id=fe5c873459a973e59854bd235a7e6b3eaa8e5fe0

It now builds cleanly with the next-20140919 tree.

Thanks!
Helge

  reply	other threads:[~2014-09-21 19:43 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-19  6:58 linux-next: Tree for Sep 19 Stephen Rothwell
2014-09-19 19:04 ` Guenter Roeck
2014-09-19 19:15 ` Guenter Roeck
2014-09-20 19:36   ` Helge Deller
2014-09-20 21:01     ` Guenter Roeck
2014-09-21 19:43       ` Helge Deller [this message]
2014-09-19 19:42 ` Guenter Roeck
2014-09-19 20:06 ` Guenter Roeck
2014-09-22 14:40   ` Christoph Hellwig
2014-09-19 20:24 ` Guenter Roeck
2014-09-22 14:35   ` Christoph Hellwig
2014-09-19 21:14 ` Guenter Roeck
2014-09-19 21:42   ` Anish Bhatt
2014-09-20  0:18     ` Guenter Roeck
2014-09-19 22:21   ` Randy Dunlap
2014-09-19 22:28     ` Anish Bhatt
2014-09-19 22:35       ` Randy Dunlap
2014-09-20  0:15     ` Guenter Roeck
2014-09-20  1:09       ` Randy Dunlap
2014-09-20  1:43         ` Anish Bhatt
2014-09-20  2:08           ` David Miller
2014-09-20  2:40             ` Guenter Roeck
  -- strict thread matches above, loose matches on Subject: below --
2025-09-19 15:05 Mark Brown
2024-09-19  5:46 Stephen Rothwell
2023-09-19  6:37 Stephen Rothwell
2022-09-19  9:47 Stephen Rothwell
2019-09-19 16:06 Mark Brown
2018-09-19  6:16 Stephen Rothwell
2017-09-19  4:15 Stephen Rothwell
2016-09-19  7:02 Stephen Rothwell
2013-09-19  3:59 Stephen Rothwell
2013-09-19  3:59 ` Stephen Rothwell

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=541F2A72.8030007@gmx.de \
    --to=deller@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=mingo@kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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.