From: Greg KH <gregkh@linuxfoundation.org>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Cc: thierry.escande@collabora.com, wnhuang@google.com,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] firmware: Google VPD: Fix memory allocation error handling
Date: Fri, 05 May 2017 19:56:47 +0000 [thread overview]
Message-ID: <20170505195647.GB7351@kroah.com> (raw)
In-Reply-To: <20170505190844.2945-1-christophe.jaillet@wanadoo.fr>
On Fri, May 05, 2017 at 09:08:44PM +0200, Christophe JAILLET wrote:
> This patch fixes several issues:
> - if the 1st 'kzalloc' fails, we dereference a NULL pointer
> - if the 2nd 'kzalloc' fails, there is a memory leak
> - if 'sysfs_create_bin_file' fails there is also a memory leak
Then it should be multiple patches, not fixing 3 things in one patch,
right?
thanks,
greg k-h
next prev parent reply other threads:[~2017-05-05 19:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-05 19:08 [PATCH] firmware: Google VPD: Fix memory allocation error handling Christophe JAILLET
2017-05-05 19:56 ` Greg KH [this message]
2017-05-06 5:02 ` Christophe JAILLET
2017-05-06 8:40 ` Dan Carpenter
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=20170505195647.GB7351@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=christophe.jaillet@wanadoo.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thierry.escande@collabora.com \
--cc=wnhuang@google.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