mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: GUO Zihua <guozihua@huawei.com>
To: <stable@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <gregkh@linuxfoundation.org>, <zohar@linux.ibm.com>,
	<paul@paul-moore.com>, <luhuaxin1@huawei.com>
Subject: [PATCH 4.19 0/3] Backport handling -ESTALE policy update failure to 4.19
Date: Wed, 1 Feb 2023 10:39:49 +0800	[thread overview]
Message-ID: <20230201023952.30247-1-guozihua@huawei.com> (raw)

This series backports patches in order to resolve the issue discussed here:
https://lore.kernel.org/selinux/389334fe-6e12-96b2-6ce9-9f0e8fcb85bf@huawei.com/

This required backporting the non-blocking LSM policy update mechanism
prerequisite patches.

Paul Moore has reviewed the non-blocking LSM policy update backport,
saying the SELinux part look good. The patchset was also reviewed by Mimi
Zohar
and everything looks ok.

I've tested the patches against the said issue and can confirm that the
issue is fixed. I've also run the LTP testcases on the fixed IMA and all
tests are passed.

This is a re-send of the original patchset as the original patchset
might have a faulty cover letter. The original patchset could be found
here:
https://patchwork.kernel.org/project/linux-integrity/list/?series=709367

GUO Zihua (1):
  ima: Handle -ESTALE returned by ima_filter_rule_match()

Janne Karhunen (2):
  LSM: switch to blocking policy update notifiers
  ima: use the lsm policy update notifier

 drivers/infiniband/core/device.c    |   4 +-
 include/linux/security.h            |  12 +--
 security/integrity/ima/ima.h        |   2 +
 security/integrity/ima/ima_main.c   |   8 ++
 security/integrity/ima/ima_policy.c | 151 ++++++++++++++++++++++------
 security/security.c                 |  23 +++--
 security/selinux/hooks.c            |   2 +-
 security/selinux/selinuxfs.c        |   2 +-
 8 files changed, 155 insertions(+), 49 deletions(-)

-- 
2.17.1


             reply	other threads:[~2023-02-01  2:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-01  2:39 GUO Zihua [this message]
2023-02-01  2:39 ` [PATCH 4.19 1/3] LSM: switch to blocking policy update notifiers GUO Zihua
2023-02-01  2:39 ` [PATCH 4.19 2/3] ima: use the lsm policy update notifier GUO Zihua
2023-02-01  2:39 ` [PATCH 4.19 3/3] ima: Handle -ESTALE returned by ima_filter_rule_match() GUO Zihua
2023-02-02 17:20 ` [PATCH 4.19 0/3] Backport handling -ESTALE policy update failure to 4.19 Sasha Levin
2023-02-03  1:10   ` Guozihua (Scott)
2023-02-03  7:44     ` Greg KH
2023-02-03  7:49       ` Greg KH
2023-02-03  7:54         ` Greg KH
2023-02-06  2:55           ` Guozihua (Scott)

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=20230201023952.30247-1-guozihua@huawei.com \
    --to=guozihua@huawei.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luhuaxin1@huawei.com \
    --cc=paul@paul-moore.com \
    --cc=stable@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®