From: Mimi Zohar <zohar@linux.ibm.com>
To: Coiby Xu <coxu@redhat.com>, RuiRui Yang <ruyang@redhat.com>
Cc: Baoquan He <bhe@redhat.com>,
linux-integrity@vger.kernel.org, kexec@lists.infradead.org
Subject: Re: [RFC PATCH] ima: add a knob to make IMA be able to be disabled
Date: Wed, 02 Apr 2025 07:25:14 -0400 [thread overview]
Message-ID: <2c53cffcae9b05783dbb6c95d3f1255e2757d596.camel@linux.ibm.com> (raw)
In-Reply-To: <h3bjnvtded2hgbhya6ugb62mnlmkjpmifa6w6wwutfd3jq326r@lzpoun5pksev>
On Wed, 2025-04-02 at 16:43 +0800, Coiby Xu wrote:
> > Coiby, would disabling just IMA-measurement, as opposed to IMA-appraisal, save
> > sufficient memory for kdump?
>
> For disabling just IMA-measurement, do you mean not enabling any measure
> rules? The more memory reserved for the kdump kernel, the less memory
> can be used by the 1st kernel. So from the perfective of kdump, we try
> to make the memory footprint as smaller as possible.
Yes, not enabling any "measure" rules and not restoring the kexec measurement
list.
next prev parent reply other threads:[~2025-04-02 11:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-31 6:16 [RFC PATCH] ima: add a knob to make IMA be able to be disabled Baoquan He
2025-03-31 6:22 ` Paul Menzel
2025-03-31 8:21 ` Baoquan He
2025-03-31 12:15 ` Mimi Zohar
2025-04-02 1:38 ` Coiby Xu
2025-04-02 1:47 ` RuiRui Yang
2025-04-02 3:30 ` Mimi Zohar
2025-04-02 8:43 ` Coiby Xu
2025-04-02 11:25 ` Mimi Zohar [this message]
2025-04-02 11:49 ` Baoquan He
2025-04-03 20:03 ` Mimi Zohar
2025-04-07 1:34 ` Baoquan He
2025-04-07 11:46 ` Mimi Zohar
2025-04-09 2:42 ` Baoquan He
2025-04-09 15:40 ` Mimi Zohar
2025-04-16 3:22 ` Baoquan He
2025-04-28 3:48 ` Coiby Xu
2025-04-29 11:39 ` Mimi Zohar
2025-05-09 5:59 ` Coiby Xu
2025-05-09 13:03 ` Mimi Zohar
2025-05-13 0:14 ` Coiby Xu
2025-05-13 3:55 ` Gao Xiang
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=2c53cffcae9b05783dbb6c95d3f1255e2757d596.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=bhe@redhat.com \
--cc=coxu@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=linux-integrity@vger.kernel.org \
--cc=ruyang@redhat.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).