From: Micah Morton <mortonm@chromium.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-security-module <linux-security-module@vger.kernel.org>
Subject: Re: linux-next: Tree for Jan 29 (security/safesetid/)
Date: Tue, 29 Jan 2019 10:21:16 -0800 [thread overview]
Message-ID: <CAJ-EccMgDvx81g-XgWymdYn_G5Ou8mgbef3GUbx-C_Ai5qF-pQ@mail.gmail.com> (raw)
In-Reply-To: <a4e95bee-e5c5-94f5-a577-d55cdd419e86@infradead.org>
I noticed you don't have the following lines (or some of the other
related security ones) in your .config.
CONFIG_SECURITY=y
CONFIG_SECURITY_WRITABLE_HOOKS=y
Seems like we need a 'depends on SECURITY' line (or something like
that) in security/safesetid/Kconfig -- let me see if that fixes things
and if so I'll upload a patch
On Tue, Jan 29, 2019 at 9:04 AM Randy Dunlap <rdunlap@infradead.org> wrote:
>
> On 1/28/19 10:11 PM, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20190125:
> >
>
> on x86_64:
>
> ld: security/safesetid/lsm.o:(.data+0x10): undefined reference to `security_hook_heads'
> ld: security/safesetid/lsm.o:(.data+0x38): undefined reference to `security_hook_heads'
> ld: security/safesetid/lsm.o: in function `safesetid_security_init':
> lsm.c:(.init.text+0x14): undefined reference to `security_add_hooks'
>
>
> Full randconfig file is attached.
>
> --
> ~Randy
next prev parent reply other threads:[~2019-01-29 18:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-29 6:11 linux-next: Tree for Jan 29 Stephen Rothwell
2019-01-29 16:30 ` linux-next: Tree for Jan 29 (net/ipv4/devinet.c) Randy Dunlap
2019-01-29 16:50 ` linux-next: Tree for Jan 29 (SLIMbus & SND_SOC_WCD9335) Randy Dunlap
2019-01-29 16:57 ` Srinivas Kandagatla
2019-01-29 17:00 ` Randy Dunlap
2019-01-29 17:04 ` linux-next: Tree for Jan 29 (security/safesetid/) Randy Dunlap
2019-01-29 18:21 ` Micah Morton [this message]
2019-01-29 18:54 ` [PATCH] LSM: SafeSetID: 'depend' on CONFIG_SECURITY mortonm
2019-01-29 19:52 ` James Morris
2019-01-29 17:17 ` linux-next: Tree for Jan 29 (security/integrity/) Randy Dunlap
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=CAJ-EccMgDvx81g-XgWymdYn_G5Ou8mgbef3GUbx-C_Ai5qF-pQ@mail.gmail.com \
--to=mortonm@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=rdunlap@infradead.org \
--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).