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: susbystem updates for v6.5
Date: Tue, 27 Jun 2023 08:28:06 -0400	[thread overview]
Message-ID: <bdea3a9112c28fd6c2c158a14b632f89dba53ac6.camel@linux.ibm.com> (raw)

Hi Linus,

Contains an i_version change, one bug fix, and three kernel doc fixes:

- Instead of IMA detecting file change by directly accesssing
i_version, it now calls vfs_getattr_nosec().

- The bug fix addresses a race condition when inserting a new node in
the iint rb-tree.

thanks,

Mimi

The following changes since commit f1fcbaa18b28dec10281551dfe6ed3a3ed80e3d6:

  Linux 6.4-rc2 (2023-05-14 12:51:40 -0700)

are available in the Git repository at:

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

for you to fetch changes up to 95526d13038c2bbddd567a4d8e39fac42484e182:

  ima: Fix build warnings (2023-06-06 09:37:23 -0400)

----------------------------------------------------------------
integrity-v6.5

----------------------------------------------------------------
Jeff Layton (1):
      IMA: use vfs_getattr_nosec to get the i_version

Roberto Sassu (3):
      evm: Complete description of evm_inode_setattr()
      evm: Fix build warnings
      ima: Fix build warnings

Tianjia Zhang (1):
      integrity: Fix possible multiple allocation in integrity_inode_get()

 security/integrity/evm/evm_crypto.c |  2 +-
 security/integrity/evm/evm_main.c   |  4 +++-
 security/integrity/iint.c           | 15 +++++++++------
 security/integrity/ima/ima_api.c    |  9 ++++++---
 security/integrity/ima/ima_main.c   | 12 ++++++++----
 security/integrity/ima/ima_modsig.c |  3 +++
 security/integrity/ima/ima_policy.c |  3 ++-
 7 files changed, 32 insertions(+), 16 deletions(-)


             reply	other threads:[~2023-06-27 12:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-27 12:28 Mimi Zohar [this message]
2023-06-28  1:01 ` 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=bdea3a9112c28fd6c2c158a14b632f89dba53ac6.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®