Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Berger <stefanb@linux.ibm.com>
To: Tushar Sugandhi <tusharsu@linux.microsoft.com>,
	zohar@linux.ibm.com, ebiederm@xmission.com, noodles@fb.com,
	bauermann@kolabnow.com, kexec@lists.infradead.org,
	linux-integrity@vger.kernel.org
Cc: code@tyhicks.com, nramas@linux.microsoft.com, paul@paul-moore.com
Subject: Re: [PATCH v2 6/7] ima: make the memory for events between kexec load and exec configurable
Date: Fri, 20 Oct 2023 17:16:47 -0400	[thread overview]
Message-ID: <15a12e79-2e90-28f7-ffa3-ff470c673099@linux.ibm.com> (raw)
In-Reply-To: <55585644-2170-d462-4d64-ca3a963b30fe@linux.microsoft.com>

On 10/20/23 16:39, Tushar Sugandhi wrote:

>
>
> On 10/12/23 17:27, Stefan Berger wrote:
>>
>> On 10/5/23 14:26, Tushar Sugandhi wrote:
>>> IMA currently allocates half a PAGE_SIZE for the extra events that 
>>> would
>>> be measured between kexec 'load' and 'execute'.  Depending on the IMA
>>> policy and the system state, that memory may not be sufficient to hold
>>> the extra IMA events measured after kexec 'load'.  The memory
>>> requirements vary from system to system and they should be 
>>> configurable.
>>>
>>> Define a Kconfig option, IMA_KEXEC_EXTRA_PAGES, to configure the number
>>> of extra pages to be allocated for IMA measurements added in the window
>>> from kexec 'load' to kexec 'execute'.
>>>
>>> Update ima_add_kexec_buffer() function to allocate memory based on the
>>> Kconfig option value, rather than the currently hardcoded one.
>>>
>>> Signed-off-by: Tushar Sugandhi<tusharsu@linux.microsoft.com>
>>> ---
>>>   security/integrity/ima/Kconfig     |  9 +++++++++
>>>   security/integrity/ima/ima_kexec.c | 13 ++++++++-----
>>>   2 files changed, 17 insertions(+), 5 deletions(-)
>>>
>>> diff --git a/security/integrity/ima/Kconfig 
>>> b/security/integrity/ima/Kconfig
>>> index 60a511c6b583..1b55cd2bcb36 100644
>>> --- a/security/integrity/ima/Kconfig
>>> +++ b/security/integrity/ima/Kconfig
>>> @@ -338,3 +338,12 @@ config IMA_DISABLE_HTABLE
>>>       default n
>>>       help
>>>          This option disables htable to allow measurement of 
>>> duplicate records.
>>> +
>>> +config IMA_KEXEC_EXTRA_PAGES
>>> +    int
>>> +    depends on IMA && IMA_KEXEC
>>> +    default 16
>>> +    help
>>> +      IMA_KEXEC_EXTRA_PAGES determines the number of extra
>>> +      pages to be allocated for IMA measurements added in the
>>> +      window from kexec 'load' to kexec 'execute'.
>>
>>
>> On ppc64 a page is 64kb. I would ask for additional kb here.
>>
>>
> Not sure I understand.  Do you mean I should make the default value of
> the config IMA_KEXEC_EXTRA_PAGES 64 or something?


No, what I mean is you should ask the user for how many extra kilobytes 
(kb) to allocate - not ask for pages.


    Stefan

>
> In code, I multiply the config value with PAGE_SIZE.  So more memory
> would be allocated on ppc64 for given default config value. Could you
> please clarify what change you are suggesting here?
>
>
> +        binary_runtime_size = ima_get_binary_runtime_size() +
> +                               sizeof(struct ima_kexec_hdr) +
> +                               (CONFIG_IMA_KEXEC_EXTRA_PAGES *
> PAGE_SIZE);
>
> ~Tushar
>
>>> diff --git a/security/integrity/ima/ima_kexec.c 
>>> b/security/integrity/ima/ima_kexec.c
>>> index 13fbbb90319b..6cd5f46a7208 100644
>>> --- a/security/integrity/ima/ima_kexec.c
>>> +++ b/security/integrity/ima/ima_kexec.c
>>> @@ -150,15 +150,18 @@ void ima_add_kexec_buffer(struct kimage *image)
>>>       int ret;
>>>       /*
>>> -     * Reserve an extra half page of memory for additional 
>>> measurements
>>> -     * added during the kexec load.
>>> +     * Reserve extra memory for measurements added in the window from
>>> +     * kexec 'load' to kexec 'execute'.
>>>        */
>>> -    binary_runtime_size = ima_get_binary_runtime_size();
>>> +    binary_runtime_size = ima_get_binary_runtime_size() +
>>> +                  sizeof(struct ima_kexec_hdr) +
>>> +                  (CONFIG_IMA_KEXEC_EXTRA_PAGES * PAGE_SIZE);
>>> +
>>>       if (binary_runtime_size >= ULONG_MAX - PAGE_SIZE)
>>>           kexec_segment_size = ULONG_MAX;
>>>       else
>>> -        kexec_segment_size = ALIGN(ima_get_binary_runtime_size() +
>>> -                       PAGE_SIZE / 2, PAGE_SIZE);
>>> +        kexec_segment_size = ALIGN(binary_runtime_size, PAGE_SIZE);
>>> +
>>>       if ((kexec_segment_size == ULONG_MAX) ||
>>>           ((kexec_segment_size >> PAGE_SHIFT) > totalram_pages() / 
>>> 2)) {
>>>           pr_err("Binary measurement list too large.\n");

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  reply	other threads:[~2023-10-20 21:24 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-05 18:25 [PATCH v2 0/7] ima: kexec: measure events between kexec load and execute Tushar Sugandhi
2023-10-05 18:25 ` [PATCH v2 1/7] ima: refactor ima_dump_measurement_list to move memory allocation to a separate function Tushar Sugandhi
2023-10-13  0:28   ` Stefan Berger
2023-10-20 20:33     ` Tushar Sugandhi
2023-10-20 21:21       ` Stefan Berger
2023-10-20 21:50         ` Tushar Sugandhi
2023-10-26 20:16   ` Mimi Zohar
2023-10-27  3:25     ` Mimi Zohar
2023-11-14 22:32       ` Tushar Sugandhi
2023-11-14 22:31     ` Tushar Sugandhi
2023-10-05 18:25 ` [PATCH v2 2/7] ima: move ima_dump_measurement_list call from kexec load to execute Tushar Sugandhi
2023-10-13  0:28   ` Stefan Berger
2023-10-20 20:35     ` Tushar Sugandhi
     [not found]   ` <989af3e9a8621f57643b67b717d9a39fdb2ffe24.camel@linux.ibm.com>
2023-11-14 22:43     ` Tushar Sugandhi
2023-11-15 22:30       ` Tushar Sugandhi
2023-10-05 18:25 ` [PATCH v2 3/7] ima: kexec: map source pages containing IMA buffer to image post kexec load Tushar Sugandhi
2023-10-13  0:29   ` Stefan Berger
2023-10-20 20:36     ` Tushar Sugandhi
2023-10-05 18:25 ` [PATCH v2 4/7] kexec: update kexec_file_load syscall to call ima_kexec_post_load Tushar Sugandhi
2023-10-05 18:26 ` [PATCH v2 5/7] ima: suspend measurements while the buffer is being copied during kexec reboot Tushar Sugandhi
2023-10-05 18:26 ` [PATCH v2 6/7] ima: make the memory for events between kexec load and exec configurable Tushar Sugandhi
2023-10-13  0:27   ` Stefan Berger
2023-10-20 20:39     ` Tushar Sugandhi
2023-10-20 21:16       ` Stefan Berger [this message]
2023-10-20 21:53         ` Tushar Sugandhi
2023-10-05 18:26 ` [PATCH v2 7/7] ima: record log size at kexec load and execute Tushar Sugandhi
2023-10-13  0:27   ` Stefan Berger
2023-10-20 20:40     ` Tushar Sugandhi
     [not found]   ` <2b95e8b9ebe10a24c7cb6fc90cb2d1342a157ed5.camel@linux.ibm.com>
2023-11-14 22:48     ` Tushar Sugandhi
     [not found] ` <8f87e7e4fe5c5a24cdc0d3e2267eeaf00825d1bb.camel@linux.ibm.com>
2023-10-27 19:51   ` [PATCH v2 0/7] ima: kexec: measure events between " Mimi Zohar
2023-11-15 19:21     ` Tushar Sugandhi
2023-11-14 23:24   ` Tushar Sugandhi

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=15a12e79-2e90-28f7-ffa3-ff470c673099@linux.ibm.com \
    --to=stefanb@linux.ibm.com \
    --cc=bauermann@kolabnow.com \
    --cc=code@tyhicks.com \
    --cc=ebiederm@xmission.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-integrity@vger.kernel.org \
    --cc=noodles@fb.com \
    --cc=nramas@linux.microsoft.com \
    --cc=paul@paul-moore.com \
    --cc=tusharsu@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