From: Dave Hansen <dave.hansen@linux.intel.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Arnd Bergmann <arnd@arndb.de>,
"open list:ABI/API" <linux-api@vger.kernel.org>,
linux-arch <linux-arch@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: Build failures in -next: sys_pkey_mprotect etc. undefined
Date: Mon, 12 Sep 2016 13:09:17 -0700 [thread overview]
Message-ID: <57D70B6D.6010208@linux.intel.com> (raw)
In-Reply-To: <9d74497b-1522-b350-42fa-49df2df48c4a@roeck-us.net>
[-- Attachment #1: Type: text/plain, Size: 860 bytes --]
On 09/12/2016 07:55 AM, Guenter Roeck wrote:
> Building h8300:allnoconfig ... failed
> Building h8300:h8300h-sim_defconfig ... failed
> Building c6x:dsk6455_defconfig ... failed
>
> [ and more builds for the same architectures ]
>
> --------------
> Error log:
> arch/h8300/kernel/built-in.o:(.data+0x480): undefined reference to
> `sys_pkey_mprotect'
> arch/h8300/kernel/built-in.o:(.data+0x484): undefined reference to
> `sys_pkey_alloc'
> arch/h8300/kernel/built-in.o:(.data+0x488): undefined reference to
> `sys_pkey_free'
So, I've done what Arnd suggested, but I don't have a working
cross-compiler than can do h8300 or c6x. Could you test the attached
patch and see if it gets things working for you?
Also, do you have a handy place to grab a cross-compiler for h8300
without having to build one? The kernel.org ones don't seem to work for
h8300.
[-- Attachment #2: fix-pkeys-arch-breakage.patch --]
[-- Type: text/x-patch, Size: 1047 bytes --]
Guenter Roeck reported breakage on the h8300 and c6x architectures
(among others) caused by the new memory protection keys syscalls.
This patch does what Arnd suggested and adds them to
kernel/sys_ni.c.
I don't have a cross-compiler for either of these architectures
handy, and kernel.org doesn't provide one either, so I have not
built this patch. Testing would be appreciated.
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Arnd Bergmann <arnd@arndb.de>
Cc: "open list:ABI/API" <linux-api@vger.kernel.org>
Cc: linux-arch@vger.kernel.org
---
b/kernel/sys_ni.c | 5 +++++
1 file changed, 5 insertions(+)
diff -puN kernel/sys_ni.c~fix-pkeys-arch-breakage kernel/sys_ni.c
--- a/kernel/sys_ni.c~fix-pkeys-arch-breakage 2016-09-12 12:50:47.801607239 -0700
+++ b/kernel/sys_ni.c 2016-09-12 12:50:47.804607374 -0700
@@ -250,3 +250,8 @@ cond_syscall(sys_execveat);
/* membarrier */
cond_syscall(sys_membarrier);
+
+/* memory protection keys */
+cond_syscall(sys_pkey_mprotect);
+cond_syscall(sys_pkey_alloc);
+cond_syscall(sys_pkey_free);
_
next prev parent reply other threads:[~2016-09-12 20:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-12 14:55 Build failures in -next: sys_pkey_mprotect etc. undefined Guenter Roeck
[not found] ` <9d74497b-1522-b350-42fa-49df2df48c4a-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
2016-09-12 14:59 ` Arnd Bergmann
2016-09-12 14:59 ` Arnd Bergmann
2016-09-12 15:03 ` Dave Hansen
2016-09-12 15:03 ` Dave Hansen
2016-09-12 20:09 ` Dave Hansen [this message]
[not found] ` <57D70B6D.6010208-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2016-09-12 20:28 ` Arnd Bergmann
2016-09-12 20:28 ` Arnd Bergmann
2016-09-12 20:33 ` Guenter Roeck
2016-09-12 20:34 ` Dave Hansen
2016-09-12 20:34 ` Dave Hansen
2016-09-12 20:32 ` Guenter Roeck
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=57D70B6D.6010208@linux.intel.com \
--to=dave.hansen@linux.intel.com \
--cc=arnd@arndb.de \
--cc=linux-api@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).