From: Tyler Hicks <tyhicks@linux.microsoft.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: gouhao@uniontech.com, stable@vger.kernel.org,
zohar@linux.vnet.ibm.com, dmitry.kasatkin@gmail.com,
jmorris@namei.org, serge@hallyn.com
Subject: Re: [PATCH 0/3] Backporting some memory leak of ima policy to 4.19+ from mainline
Date: Fri, 7 Oct 2022 13:31:45 -0500 [thread overview]
Message-ID: <Y0BwkcMaWnuqOXLI@sequoia> (raw)
In-Reply-To: <YzmvvJx1fMOD6SMY@kroah.com>
On 2022-10-02 17:35:24, Greg KH wrote:
> On Fri, Sep 30, 2022 at 03:49:34PM +0800, gouhao@uniontech.com wrote:
> > From: Gou Hao <gouhao@uniontech.com>
> >
> > patch1: is memory leak of audit rule
> > patch2~3: is memory leak about 'fsname' field of struct ima_rule_entry
> >
> > Tyler Hicks (3):
> > ima: Have the LSM free its audit rule
> > ima: Free the entire rule when deleting a list of rules
> > ima: Free the entire rule if it fails to parse
> >
> > security/integrity/ima/ima.h | 5 +++++
> > security/integrity/ima/ima_policy.c | 24 ++++++++++++++++++------
> > 2 files changed, 23 insertions(+), 6 deletions(-)
> >
> > --
> > 2.20.1
> >
>
> Now queued up, thanks.
I know these patches have been already applied and were even released a
couple days ago but I wanted to say that I reviewed these backports,
since they were a little tricky, and they all look good. Thanks for
doing this, Gou!
Tyler
>
> greg k-h
>
prev parent reply other threads:[~2022-10-07 18:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-30 7:49 [PATCH 0/3] Backporting some memory leak of ima policy to 4.19+ from mainline gouhao
2022-09-30 7:49 ` [PATCH 1/3] ima: Have the LSM free its audit rule gouhao
2022-09-30 7:49 ` [PATCH 2/3] ima: Free the entire rule when deleting a list of rules gouhao
2022-09-30 7:49 ` [PATCH 3/3] ima: Free the entire rule if it fails to parse gouhao
2022-10-02 15:35 ` [PATCH 0/3] Backporting some memory leak of ima policy to 4.19+ from mainline Greg KH
2022-10-07 18:31 ` Tyler Hicks [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=Y0BwkcMaWnuqOXLI@sequoia \
--to=tyhicks@linux.microsoft.com \
--cc=dmitry.kasatkin@gmail.com \
--cc=gouhao@uniontech.com \
--cc=gregkh@linuxfoundation.org \
--cc=jmorris@namei.org \
--cc=serge@hallyn.com \
--cc=stable@vger.kernel.org \
--cc=zohar@linux.vnet.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