From: Mimi Zohar <zohar@linux.ibm.com>
To: Jianglei Nie <niejianglei2021@163.com>,
	dmitry.kasatkin@gmail.com, jmorris@namei.org, serge@hallyn.com
Cc: linux-integrity@vger.kernel.org,
	linux-security-module@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] ima/evm: Fix potential memory leak in ima_init_crypto()
Date: Tue, 12 Jul 2022 07:40:18 -0400	[thread overview]
Message-ID: <7dd513fba6c248327a9118e8dafe628d13dde495.camel@linux.ibm.com> (raw)
In-Reply-To: <20220712011037.2328591-1-niejianglei2021@163.com>
On Tue, 2022-07-12 at 09:10 +0800, Jianglei Nie wrote:
> On failure to allocate the SHA1 tfm, IMA fails to initialize and exits
> without freeing the ima_algo_array. Add the missing kfree() for
> ima_algo_array to avoid the potential memory leak.
> 
> Signed-off-by: Jianglei Nie <niejianglei2021@163.com>
Thanks, Jianglei.  This patch is now queued in next-integrity/next-
integrity-testing.
Mimi
     prev parent reply	other threads:[~2022-07-12 11:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-12  1:10 [PATCH v2] ima/evm: Fix potential memory leak in ima_init_crypto() Jianglei Nie
2022-07-12 11:40 ` 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=7dd513fba6c248327a9118e8dafe628d13dde495.camel@linux.ibm.com \
    --to=zohar@linux.ibm.com \
    --cc=dmitry.kasatkin@gmail.com \
    --cc=jmorris@namei.org \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=niejianglei2021@163.com \
    --cc=serge@hallyn.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;
as well as URLs for NNTP newsgroup(s).