From: Mimi Zohar <zohar@linux.ibm.com>
To: Greg KH <gregkh@linuxfoundation.org>, GUO Zihua <guozihua@huawei.com>
Cc: stable@vger.kernel.org, paul@paul-moore.com,
linux-integrity@vger.kernel.org, luhuaxin1@huawei.com
Subject: Re: [PATCH v6 0/3] ima: Fix IMA mishandling of LSM based rule during
Date: Tue, 10 Jan 2023 08:30:55 -0500 [thread overview]
Message-ID: <4b867a8508e9da63d4dfa276f89f3f636d4e4e4d.camel@linux.ibm.com> (raw)
In-Reply-To: <Y7a45tx4tvV6hDuC@kroah.com>
On Thu, 2023-01-05 at 12:47 +0100, Greg KH wrote:
> On Thu, Jan 05, 2023 at 02:23:09PM +0800, GUO Zihua wrote:
> > Backports the following three patches to fix the issue of IMA mishandling
> > LSM based rule during LSM policy update, causing a file to match an
> > unexpected rule.
> >
> > v6:
> > Removed the redundent i in ima_free_rule().
>
> Given the huge numbers of revisions in this series, I suggest working
> together with the relevant subsystem maintainers to get a final,
> working, agreed-apon version before submitting it again.
There was one minor change to v6, which is addressed in v7. Paul has
reviewed the LSM/SELinux pieces. I'd appreciate v7 of this patch set
be applied to stable 4.19.
FYI, commit c7423dbdbc9e ("ima: Handle -ESTALE returned by
ima_filter_rule_match()") has already been backported to other stable
branches.
--
thanks,
Mimi
prev parent reply other threads:[~2023-01-10 13:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-05 6:23 [PATCH v6 0/3] ima: Fix IMA mishandling of LSM based rule during GUO Zihua
2023-01-05 6:23 ` [PATCH v6 1/3] LSM: switch to blocking policy update notifiers GUO Zihua
2023-01-05 6:23 ` [PATCH v6 2/3] ima: use the lsm policy update notifier GUO Zihua
2023-01-05 17:35 ` Mimi Zohar
2023-01-05 6:23 ` [PATCH v6 3/3] ima: Handle -ESTALE returned by ima_filter_rule_match() GUO Zihua
2023-01-05 11:47 ` [PATCH v6 0/3] ima: Fix IMA mishandling of LSM based rule during Greg KH
2023-01-10 13:30 ` Mimi Zohar [this message]
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=4b867a8508e9da63d4dfa276f89f3f636d4e4e4d.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=gregkh@linuxfoundation.org \
--cc=guozihua@huawei.com \
--cc=linux-integrity@vger.kernel.org \
--cc=luhuaxin1@huawei.com \
--cc=paul@paul-moore.com \
--cc=stable@vger.kernel.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