From: <gregkh@linuxfoundation.org>
To: jeffy.chen@rock-chips.com, gregkh@linuxfoundation.org,
snitzer@redhat.com
Cc: <stable@vger.kernel.org>, <stable-commits@vger.kernel.org>
Subject: Patch "dm crypt: fix memory leak in crypt_ctr_cipher_old()" has been added to the 4.13-stable tree
Date: Tue, 10 Oct 2017 17:29:27 +0200 [thread overview]
Message-ID: <150764936720119@kroah.com> (raw)
This is a note to let you know that I've just added the patch titled
dm crypt: fix memory leak in crypt_ctr_cipher_old()
to the 4.13-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
dm-crypt-fix-memory-leak-in-crypt_ctr_cipher_old.patch
and it can be found in the queue-4.13 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@vger.kernel.org> know about it.
>From bd86e32059526e2d0d13ca1e4447dfbbddb6e5cc Mon Sep 17 00:00:00 2001
From: Jeffy Chen <jeffy.chen@rock-chips.com>
Date: Wed, 27 Sep 2017 20:28:57 +0800
Subject: dm crypt: fix memory leak in crypt_ctr_cipher_old()
From: Jeffy Chen <jeffy.chen@rock-chips.com>
commit bd86e32059526e2d0d13ca1e4447dfbbddb6e5cc upstream.
Fix memory leak of cipher_api.
Fixes: 33d2f09fcb35 (dm crypt: introduce new format of cipher with "capi:" prefix)
Signed-off-by: Jeffy Chen <jeffy.chen@rock-chips.com>
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
---
drivers/md/dm-crypt.c | 1 +
1 file changed, 1 insertion(+)
--- a/drivers/md/dm-crypt.c
+++ b/drivers/md/dm-crypt.c
@@ -2470,6 +2470,7 @@ static int crypt_ctr_cipher_old(struct d
kfree(cipher_api);
return ret;
}
+ kfree(cipher_api);
return 0;
bad_mem:
Patches currently in stable-queue which might be from jeffy.chen@rock-chips.com are
queue-4.13/dm-crypt-fix-memory-leak-in-crypt_ctr_cipher_old.patch
reply other threads:[~2017-10-10 15:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=150764936720119@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jeffy.chen@rock-chips.com \
--cc=snitzer@redhat.com \
--cc=stable-commits@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.