From: Greg KH <greg@kroah.com>
To: Ming Lei <tom.leiming@gmail.com>
Cc: linux-kernel@vger.kernel.org, catalin.marinas@arm.com,
dwmw2@infradead.org, kay.sievers@vrfy.org
Subject: Re: [PATCH] driver core:firmware_class:fix memory leak of page pointers array
Date: Thu, 16 Jul 2009 15:41:40 -0700 [thread overview]
Message-ID: <20090716224140.GA12401@kroah.com> (raw)
In-Reply-To: <d82e647a0907160622y2ec1798eue1310b7feaf79114@mail.gmail.com>
On Thu, Jul 16, 2009 at 09:22:33PM +0800, Ming Lei wrote:
> 2009/7/11 Ming Lei <tom.leiming@gmail.com>:
> > On Fri, 10 Jul 2009 10:36:49 -0700
> > Greg KH <greg@kroah.com> wrote:
> >
> >> On Thu, Jul 09, 2009 at 08:20:48AM +0800, Ming Lei wrote:
> >> > 2009/7/9 <tom.leiming@gmail.com>:
> >> > > From: Ming Lei <tom.leiming@gmail.com>
> >> > >
> >> > > The page pointers array is allocated in fw_realloc_buffer()
> >> > > called by firmware_data_write(), and should be freed in release
> >> > > function of firmware device.
> >> > >
> >> > > Signed-off-by:Ming Lei <tom.leiming@gmail.com>
> >> > > Reported-by:Catalin Marinas <catalin.marinas@arm.com>
> >> > > Acked-by: David Woodhouse <David.Woodhouse@intel.com>
> >> >
> >> > ---
> >> > This patch is against Catalin Marinas's patch:
> >> > [PATCH] Free struct device in fw_dev_release()
> >>
> >> Hm, I never got a final version of that patch, care to send it to me?
>
> Hi,Greg
>
> Care to queue the patch into your driver-core tree and send it to -rc4?
Now queued up.
thanks,
greg k-h
prev parent reply other threads:[~2009-07-16 22:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-09 0:16 [PATCH] driver core:firmware_class:fix memory leak of page pointers array tom.leiming
2009-07-09 0:20 ` Ming Lei
2009-07-10 17:36 ` Greg KH
2009-07-11 3:11 ` Ming Lei
2009-07-16 13:22 ` Ming Lei
2009-07-16 22:41 ` Greg KH [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=20090716224140.GA12401@kroah.com \
--to=greg@kroah.com \
--cc=catalin.marinas@arm.com \
--cc=dwmw2@infradead.org \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tom.leiming@gmail.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