From: Paul Moore <paul@paul-moore.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ondrej Mosnacek <omosnace@redhat.com>
Subject: Re: linux-next: build failure after merge of the selinux tree
Date: Tue, 2 Apr 2019 21:25:18 -0400 [thread overview]
Message-ID: <CAHC9VhRbYZzd=526r4k6d12Rs=PKx0ro4+04BKfAN-ozarc2cg@mail.gmail.com> (raw)
In-Reply-To: <20190403122212.68a9964d@canb.auug.org.au>
On Tue, Apr 2, 2019 at 9:22 PM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi Paul,
>
> After merging the selinux tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> x86_64-linux-gnu-ld: security/selinux/hooks.o: in function `selinux_kernfs_init_security':
> hooks.c:(.text+0x8f7d): undefined reference to `kernfs_xattr_get'
> x86_64-linux-gnu-ld: hooks.c:(.text+0x8ff5): undefined reference to `kernfs_xattr_get'
> x86_64-linux-gnu-ld: hooks.c:(.text+0x91b5): undefined reference to `kernfs_xattr_set'
>
> Caused by commit
>
> 1991af34fa26 ("kernfs: fix xattr name handling in LSM helpers")
>
> I have used the selinux tree from next-20190402 for today.
Hi Stephen,
My apologies, I just noticed the same failure and removed the commit
from selinux/next. I let Ondrej know and I would expect he'll have an
updated patch shortly.
--
paul moore
www.paul-moore.com
next prev parent reply other threads:[~2019-04-03 1:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-03 1:22 linux-next: build failure after merge of the selinux tree Stephen Rothwell
2019-04-03 1:25 ` Paul Moore [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-27 2:10 Stephen Rothwell
2024-03-27 13:13 ` Paul Moore
2021-10-05 3:10 Stephen Rothwell
2021-10-05 13:57 ` Paul Moore
2019-12-10 1:40 Stephen Rothwell
2019-12-10 2:25 ` Paul Moore
2019-03-19 1:40 Stephen Rothwell
2019-03-19 17:11 ` Paul Moore
2017-05-22 2:48 Stephen Rothwell
2017-05-22 21:12 ` Paul Moore
2017-05-22 21:16 ` Daniel Jurgens
2017-01-10 1:27 Stephen Rothwell
2017-01-11 3:11 ` Paul Moore
2017-02-10 2:50 ` Stephen Rothwell
2017-02-10 12:34 ` Paul Moore
2012-01-05 4:24 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='CAHC9VhRbYZzd=526r4k6d12Rs=PKx0ro4+04BKfAN-ozarc2cg@mail.gmail.com' \
--to=paul@paul-moore.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=omosnace@redhat.com \
--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 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).