linux-kernel - Re: Build failures in -next: sys_pkey

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <57D6C3D7.2040606@linux.intel.com>
Date:   Mon, 12 Sep 2016 08:03:51 -0700
From:   Dave Hansen <dave.hansen@...ux.intel.com>
To:     Arnd Bergmann <arnd@...db.de>, Guenter Roeck <linux@...ck-us.net>
Cc:     Thomas Gleixner <tglx@...utronix.de>,
        "open list:ABI/API" <linux-api@...r.kernel.org>,
        linux-arch <linux-arch@...r.kernel.org>,
        linux-kernel@...r.kernel.org
Subject: Re: Build failures in -next: sys_pkey_mprotect etc. undefined

On 09/12/2016 07:59 AM, Arnd Bergmann wrote:
> On Monday, September 12, 2016 7:55:33 AM CEST 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'
>>
>> Other architectures (frv, xtensa, score) currently fail to build for other reasons,
>> so I don't really know if the above are the only ones affected.
> 
> I think the best solution would be to add them to kernel/sys_ni.c so we can
> assign syscall numbers for all architectures regardless of whether they use it
> or not (most of them will never use these AFAICT).

Urg, sorry about the breakage.  I'll see if I can reproduce it and get a
patch out later today that does this.