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 updates for v5.16
Date: Tue, 02 Nov 2021 06:41:09 -0400 [thread overview]
Message-ID: <3f066f52d4937414a9e01c7f46a714e988e6196a.camel@linux.ibm.com> (raw)
Hi Linus,
Other than the new gid IMA policy rule support and the RCU locking fix,
the couple of remaining changes are minor/trivial (e.g.
__ro_after_init, replacing strscpy).
thanks,
Mimi
The following changes since commit 6880fa6c56601bb8ed59df6c30fd390cc5f6dd8f:
Linux 5.15-rc1 (2021-09-12 16:28:37 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/zohar/linux-integrity.git tags/integrity-v5.16
for you to fetch changes up to 32ba540f3c2a7ef61ed5a577ce25069a3d714fc9:
evm: mark evm_fixmode as __ro_after_init (2021-10-28 18:52:49 -0400)
----------------------------------------------------------------
integrity-v5.16
----------------------------------------------------------------
Alex Henrie (1):
ima: fix uid code style problems
Austin Kim (1):
evm: mark evm_fixmode as __ro_after_init
Curtis Veit (1):
ima: add gid support
Petr Vorel (2):
ima_policy: Remove duplicate 'the' in docs comment
ima: Use strscpy instead of strlcpy
liqiong (1):
ima: fix deadlock when traversing "ima_default_rules".
Documentation/ABI/testing/ima_policy | 8 +-
security/integrity/evm/evm_main.c | 2 +-
security/integrity/ima/ima_api.c | 2 +-
security/integrity/ima/ima_policy.c | 243 ++++++++++++++++++++++++++++-------
4 files changed, 208 insertions(+), 47 deletions(-)
next reply other threads:[~2021-11-02 10:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-02 10:41 Mimi Zohar [this message]
2021-11-02 18:37 ` [GIT PULL] integrity subsystem updates for v5.16 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=3f066f52d4937414a9e01c7f46a714e988e6196a.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