linux-kernel - Re: scripts/selinux build error in 4.14 after glibc update

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: <20190423132926.GK17719@sasha-vm>
Date:   Tue, 23 Apr 2019 09:29:26 -0400
From:   Sasha Levin <sashal@...nel.org>
To:     Paul Moore <paul@...l-moore.com>
Cc:     Nathan Chancellor <natechancellor@...il.com>,
        Stephen Smalley <sds@...ho.nsa.gov>,
        Eric Paris <eparis@...isplace.org>, selinux@...r.kernel.org,
        linux-kernel@...r.kernel.org, stable@...r.kernel.org,
        Nicolas Iooss <nicolas.iooss@....org>
Subject: Re: scripts/selinux build error in 4.14 after glibc update

On Mon, Apr 22, 2019 at 09:59:47PM -0400, Paul Moore wrote:
>On Mon, Apr 22, 2019 at 5:00 PM Nathan Chancellor
><natechancellor@...il.com> wrote:
>> Hi all,
>>
>> After a glibc update to 2.29, my 4.14 builds started failing like so:
>
>...
>
>>   HOSTCC  scripts/selinux/genheaders/genheaders
>> In file included from scripts/selinux/genheaders/genheaders.c:19:
>> ./security/selinux/include/classmap.h:245:2: error: #error New address family defined, please update secclass_map.
>>  #error New address family defined, please update secclass_map.
>>   ^~~~~
>
>This is a known problem that has a fix in the selinux/next branch and
>will be going up to Linus during the next merge window.  The fix is
>quite small and should be relatively easy for you to backport to your
>kernel build if you are interested; the patch can be found at the
>archive link below:
>
>https://lore.kernel.org/selinux/20190225005528.28371-1-paulo@paulo.ac

Why is it waiting for the next merge window? It fixes a build bug that
people hit.

--
Thanks,
Sasha