mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mimi Zohar <zohar@linux.ibm.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-integrity <linux-integrity@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] integrity: subsystem fixes for v6.17
Date: Thu, 31 Jul 2025 08:52:07 -0400	[thread overview]
Message-ID: <807ead8fdb2761721a4d79b89efb385420a0d6f0.camel@linux.ibm.com> (raw)

Hi Linus,

With hesitancy, I'm sending this pull request containing a single commit to
permit disabling IMA from the boot command line for just the kdump kernel. The
exception itself sort of makes sense. My concern is that exceptions do not
remain as exceptions, but somehow morph to become the norm [1].

Permit disabling IMA from the boot command line as an exception for just the
kdump kernel.

[1]
https://lore.kernel.org/linux-integrity/b1b5feaa93922c9b5a8f1a1e41385d266fe640ce.camel@linux.ibm.com/

thanks,

Mimi

The following changes since commit e04c78d86a9699d136910cfc0bdcf01087e3267e:

  Linux 6.16-rc2 (2025-06-15 13:49:41 -0700)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/zohar/linux-integrity.git/ tags/integrity-v6.17

for you to fetch changes up to aa9bb1b32594cd67cafd29b330b158128b503882:

  ima: add a knob ima= to allow disabling IMA in kdump kernel (2025-06-16 09:15:13 -0400)

----------------------------------------------------------------
integrity-v6.17

----------------------------------------------------------------
Baoquan He (1):
      ima: add a knob ima= to allow disabling IMA in kdump kernel

 Documentation/admin-guide/kernel-parameters.txt |  5 +++++
 security/integrity/ima/ima_main.c               | 26 +++++++++++++++++++++++++
 2 files changed, 31 insertions(+)

             reply	other threads:[~2025-07-31 12:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-31 12:52 Mimi Zohar [this message]
2025-07-31 19:07 ` pr-tracker-bot

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=807ead8fdb2761721a4d79b89efb385420a0d6f0.camel@linux.ibm.com \
    --to=zohar@linux.ibm.com \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®