From: Sasha Levin <sashal@kernel.org>
To: Paul Moore <paul@paul-moore.com>
Cc: Nathan Chancellor <natechancellor@gmail.com>,
Stephen Smalley <sds@tycho.nsa.gov>,
Eric Paris <eparis@parisplace.org>,
selinux@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, Nicolas Iooss <nicolas.iooss@m4x.org>
Subject: Re: scripts/selinux build error in 4.14 after glibc update
Date: Tue, 23 Apr 2019 09:29:26 -0400 [thread overview]
Message-ID: <20190423132926.GK17719@sasha-vm> (raw)
In-Reply-To: <CAHC9VhTtz3OA3EchaZaAeg=DxoGoz_WFdj+Mi9nd9i+cmjmuJA@mail.gmail.com>
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@gmail.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
next prev parent reply other threads:[~2019-04-23 13:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-22 21:00 scripts/selinux build error in 4.14 after glibc update Nathan Chancellor
2019-04-23 1:59 ` Paul Moore
2019-04-23 2:26 ` Nathan Chancellor
2019-04-23 13:29 ` Sasha Levin [this message]
2019-04-23 13:43 ` Paul Moore
2019-04-29 12:40 ` Greg KH
2019-04-29 14:02 ` Paul Moore
2019-04-29 14:09 ` Greg KH
2019-04-29 14:47 ` Paul Moore
2019-04-29 14:52 ` Greg KH
2019-04-29 22:37 ` Paul Moore
2019-04-30 8:49 ` Greg KH
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=20190423132926.GK17719@sasha-vm \
--to=sashal@kernel.org \
--cc=eparis@parisplace.org \
--cc=linux-kernel@vger.kernel.org \
--cc=natechancellor@gmail.com \
--cc=nicolas.iooss@m4x.org \
--cc=paul@paul-moore.com \
--cc=sds@tycho.nsa.gov \
--cc=selinux@vger.kernel.org \
--cc=stable@vger.kernel.org \
/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