From: rdunlap@infradead.org (Randy Dunlap)
To: linux-security-module@vger.kernel.org
Subject: [PATCH] security: export security_kernel_load_data to fix firmware_loader build
Date: Thu, 19 Jul 2018 15:40:27 -0700 [thread overview]
Message-ID: <41df8eb0-865f-3e53-eb13-cde642396cf7@infradead.org> (raw)
In-Reply-To: <1532039957.4196.2.camel@linux.ibm.com>
On 07/19/2018 03:39 PM, Mimi Zohar wrote:
> Thanks, Randy.
>
> On Thu, 2018-07-19 at 13:15 -0700, Randy Dunlap wrote:
>> From: Randy Dunlap <rdunlap@infradead.org>
>>
>> Fix build error when CONFIG_FW_LOADER=m, CONFIG_FW_LOADER_USER_HELPER=y,
>> CONFIG_FW_LOADER_USER_HELPER_FALLBACK=y, and CONFIG_SECURITY=y:
>>
>> ERROR: "security_kernel_load_data" [drivers/base/firmware_loader/firmware_class.ko] undefined!
>>
>> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
>> Cc: James Morris <jmorris@namei.org>
>> Cc: "Serge E. Hallyn" <serge@hallyn.com>
>> Cc: linux-security-module at vger.kernel.org
>> Cc: Luis R. Rodriguez <mcgrof@kernel.org>
>> ---
>> security/security.c | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> --- linux-next-20180717.orig/security/security.c
>> +++ linux-next-20180717/security/security.c
>> @@ -1121,6 +1121,7 @@ int security_kernel_load_data(enum kerne
>> return ret;
>> return ima_load_data(id);
>> }
>> +EXPORT_SYMBOL_GPL(security_kernel_load_data);
>
> Arnd Bergmann already posted a similar patch, which is now staged in
> James' tree.
>
> Mimi
Good. Thanks.
--
~Randy
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2018-07-19 22:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-19 20:15 [PATCH] security: export security_kernel_load_data to fix firmware_loader build Randy Dunlap
2018-07-19 22:39 ` Mimi Zohar
2018-07-19 22:40 ` Randy Dunlap [this message]
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=41df8eb0-865f-3e53-eb13-cde642396cf7@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-security-module@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;
as well as URLs for NNTP newsgroup(s).