From: Brian Norris <computersforpeace@gmail.com>
To: Insu Yun <wuninsu@gmail.com>
Cc: dwmw2@infradead.org, linux-mtd@lists.infradead.org,
linux-kernel@vger.kernel.org, taesoo@gatech.edu,
yeongjin.jang@gatech.edu, insu@gatech.edu, changwoo@gatech.edu
Subject: Re: [PATCH] mtd: fixing memory leak and handling failed kmalloc
Date: Wed, 6 Jan 2016 17:24:24 -0800 [thread overview]
Message-ID: <20160107012424.GV109450@google.com> (raw)
In-Reply-To: <1451414709-8581-1-git-send-email-wuninsu@gmail.com>
On Tue, Dec 29, 2015 at 01:45:09PM -0500, Insu Yun wrote:
> kmalloc needs to be handled when failing in memory pressure.
> Also, it has memory leak in error routine.
>
> Signed-off-by: Insu Yun <wuninsu@gmail.com>
Applied to l2-mtd.git
prev parent reply other threads:[~2016-01-07 1:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-29 18:45 [PATCH] mtd: fixing memory leak and handling failed kmalloc Insu Yun
2016-01-07 1:24 ` Brian Norris [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=20160107012424.GV109450@google.com \
--to=computersforpeace@gmail.com \
--cc=changwoo@gatech.edu \
--cc=dwmw2@infradead.org \
--cc=insu@gatech.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=taesoo@gatech.edu \
--cc=wuninsu@gmail.com \
--cc=yeongjin.jang@gatech.edu \
/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).