From: Stephen Smalley <stephen.smalley.work@gmail.com>
To: Lakshmi Ramasubramanian <nramas@linux.microsoft.com>
Cc: Mimi Zohar <zohar@linux.ibm.com>,
Casey Schaufler <casey@schaufler-ca.com>,
Tyler Hicks <tyhicks@linux.microsoft.com>,
sashal@kernel.org, James Morris <jmorris@namei.org>,
linux-integrity@vger.kernel.org,
SElinux list <selinux@vger.kernel.org>,
LSM List <linux-security-module@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v5 3/4] LSM: Define SELinux function to measure state and policy
Date: Tue, 4 Aug 2020 11:20:24 -0400 [thread overview]
Message-ID: <0fa0b1f3-6226-c307-0f11-8b3a881a070e@gmail.com> (raw)
In-Reply-To: <3e766eed-7a0b-afca-6139-ac43dea053d7@linux.microsoft.com>
On 8/3/20 6:08 PM, Lakshmi Ramasubramanian wrote:
> On 8/3/20 2:07 PM, Stephen Smalley wrote:
>
>>>>> [ 68.870715] irq event stamp: 23486085
>>>>> [ 68.870715] hardirqs last enabled at (23486085):
>>>>> [<ffffffffaa419406>] _raw_spin_unlock_irqrestore+0x46/0x60
>>>>> [ 68.870715] hardirqs last disabled at (23486084):
>>>>> [<ffffffffaa419443>] _raw_spin_lock_irqsave+0x23/0x90
>>>>> [ 68.870715] softirqs last enabled at (23486074):
>>>>> [<ffffffffaa8004f3>] __do_softirq+0x4f3/0x662
>>>>> [ 68.870715] softirqs last disabled at (23486067):
>>>>> [<ffffffffaa601072>] asm_call_on_stack+0x12/0x20
>>>>> [ 68.870715] ---[ end trace fb02740ff6f4d0cd ]---
>>>>
>>>> I think one issue here is that systemd loads SELinux policy first,
>>>> then IMA policy, so it doesn't know whether it needs to measure
>>>> SELinux policy on first policy load, and another issue is that the
>>>> policy is too large to just queue the policy data itself this way
>>>> (or you need to use an allocator that can handle larger sizes).
>>>>
>>>
>>> The problem seems to be that a lock is held when the IMA hook to
>>> measure the LSM state is called. So memory allocation is not
>>> allowed, but the hook is doing an allocation. I'll address this -
>>> thanks for catching it.
>>>
>>> I have the following CONFIGs enabled, but I still don't see the
>>> above issue on my machine.
>>>
>> The warning has to do with the memory allocation order being above
>> the max order supported for kmalloc. I think the problem is that
>> ima_alloc_data_entry() is using kmemdup() to duplicate a payload of
>> arbitrary size. Policies on e.g. Fedora can be quite large, so you
>> can't assume they can be allocated with kmalloc and friends.
>>
>
> Thanks for clarifying. Yes ima_alloc_entry() does use kmemdup to save
> the given buffer (to be measured) until IMA loads custom policy.
>
> On my machine the SELinux policy size is about 2MB.
>
> Perhaps vmalloc would be better than using kmalloc? If there are
> better options for such large buffer allocation, please let me know.
kvmalloc() can be used to select whichever one is most appropriate.
next prev parent reply other threads:[~2020-08-04 15:20 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-30 3:47 [PATCH v5 0/4] LSM: Measure security module data Lakshmi Ramasubramanian
2020-07-30 3:47 ` [PATCH v5 1/4] IMA: Add func to measure LSM state and policy Lakshmi Ramasubramanian
2020-07-30 15:02 ` Tyler Hicks
2020-07-30 15:15 ` Lakshmi Ramasubramanian
2020-07-30 15:17 ` Tyler Hicks
2020-07-30 16:19 ` Casey Schaufler
2020-07-30 16:33 ` Lakshmi Ramasubramanian
2020-07-30 3:47 ` [PATCH v5 2/4] IMA: Define IMA hooks " Lakshmi Ramasubramanian
2020-07-30 15:04 ` Tyler Hicks
2020-07-30 3:47 ` [PATCH v5 3/4] LSM: Define SELinux function to measure " Lakshmi Ramasubramanian
2020-08-03 15:11 ` Stephen Smalley
2020-08-03 16:14 ` Lakshmi Ramasubramanian
2020-08-03 20:00 ` Stephen Smalley
2020-08-03 20:29 ` Stephen Smalley
2020-08-03 20:37 ` Lakshmi Ramasubramanian
2020-08-03 21:07 ` Stephen Smalley
2020-08-03 22:08 ` Lakshmi Ramasubramanian
2020-08-04 15:20 ` Stephen Smalley [this message]
2020-08-04 15:29 ` Stephen Smalley
2020-08-04 15:57 ` Lakshmi Ramasubramanian
2020-07-30 3:47 ` [PATCH v5 4/4] IMA: Handle early boot data measurement Lakshmi Ramasubramanian
2020-07-30 18:02 ` Lakshmi Ramasubramanian
2020-07-30 20:04 ` Tyler Hicks
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=0fa0b1f3-6226-c307-0f11-8b3a881a070e@gmail.com \
--to=stephen.smalley.work@gmail.com \
--cc=casey@schaufler-ca.com \
--cc=jmorris@namei.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=nramas@linux.microsoft.com \
--cc=sashal@kernel.org \
--cc=selinux@vger.kernel.org \
--cc=tyhicks@linux.microsoft.com \
--cc=zohar@linux.ibm.com \
/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).