From: Greg KH <greg@kroah.com>
To: Pavan Savoy <pavan_savoy@yahoo.co.in>
Cc: Tomas Winkler <tomas.winkler@intel.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] firmware_class: fix memory leak - free allocated pages
Date: Tue, 4 May 2010 08:47:33 -0700 [thread overview]
Message-ID: <20100504154733.GA24636@kroah.com> (raw)
In-Reply-To: <698815.43605.qm@web94909.mail.in2.yahoo.com>
On Tue, May 04, 2010 at 08:07:33PM +0530, Pavan Savoy wrote:
>
> --- On Tue, 4/5/10, Greg KH <greg@kroah.com> wrote:
>
> > From: Greg KH <greg@kroah.com>
> > Subject: Re: [PATCH v3] firmware_class: fix memory leak - free allocated pages
> > To: "Pavan Savoy" <pavan_savoy@yahoo.co.in>
> > Cc: "Tomas Winkler" <tomas.winkler@intel.com>, linux-kernel@vger.kernel.org
> > Date: Tuesday, 4 May, 2010, 7:33 PM
> > On Tue, May 04, 2010 at 12:16:44AM
> > +0530, Pavan Savoy wrote:
> > >
> > >
> > > --- On Mon, 3/5/10, Greg KH <greg@kroah.com>
> > wrote:
> > >
> > > > From: Greg KH <greg@kroah.com>
> > > > Subject: Re: [PATCH v3] firmware_class: fix
> > memory leak - free allocated pages
> > > > To: "Tomas Winkler" <tomas.winkler@intel.com>
> > > > Cc: "Greg Kroah-Hartman" <gregkh@suse.de>,
> > linux-kernel@vger.kernel.org,
> > "David Woodhouse" <dwmw2@infradead.org>,
> > "Kay Sievers" <kay.sievers@vrfy.org>,
> > "David Woodhouse" <David.Woodhouse@intel.com>,
> > "Johannes Berg" <johannes@sipsolutions.net>,
> > "Ming Lei" <tom.leiming@gmail.com>,
> > "Catalin Marinas" <catalin.marinas@arm.com>
> > > > Date: Monday, 3 May, 2010, 10:34 PM
> > > > On Sun, May 02, 2010 at 11:21:21AM
> > > > +0300, Tomas Winkler wrote:
> > > > > From: David Woodhouse <David.Woodhouse@intel.com>
> > > > >
> > > > > fix memory leak introduced by the patch
> > 6e03a201bbe:
> > > > > firmware: speed up request_firmware()
> > > > >
> > > > > 1. vfree won't release pages there were
> > allocated
> > > > explicitly and mapped
> > > > > using vmap. The memory has to be vunmap-ed
> > and the
> > > > pages needs
> > > > > to be freed explicitly
> > > > >
> > > > > 2. page array is moved into the 'struct
> > > > > firmware' so that we can free it from
> > > > release_firmware()
> > > > > and not only in fw_dev_release()
> > > > >
> > > > > The fix doesn't break the firmware load
> > speed.
> > > > >
> > > > > Cc: Johannes Berg <johannes@sipsolutions.net>
> > > > > Cc: Greg Kroah-Hartman <gregkh@suse.de>
> > > > > Cc: Ming Lei <tom.leiming@gmail.com>
> > > > > Cc: Catalin Marinas <catalin.marinas@arm.com>
> > > > > Singed-off-by: Kay Sievers <kay.sievers@vrfy.org>
> > > > > Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
> > > > > Signed-off-by: Tomas Winkler <tomas.winkler@intel.com>
> > > > > ---
> > > > > V2: fix authorship of the patch
> > > > > V3: fix const struct firmware breakage
> > > >
> > > > Thanks, this looks much better, I've applied it
> > now.
> > >
> > > Sorry to bump-in the middle.
> > > But as a user of firmware class, what should now my
> > fw_entry structure be?
> > > const struct firmware *fw_entry or,
> > > struct firmware *fw_entry - without the const ..
> >
> > You should leave it to be whatever it was before this
> > patch, it has not
> > changed anything now.
>
> Ok, However this patch has changed the release_firmware,
> -release_firmware(const struct firmware *fw)
> +release_firmware(struct firmware *fw)
Does your code now complain about a warning? If so, do you have a
pointer to it?
thanks,
greg k-h
next prev parent reply other threads:[~2010-05-04 15:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-02 8:21 [PATCH v3] firmware_class: fix memory leak - free allocated pages Tomas Winkler
2010-05-03 17:04 ` Greg KH
2010-05-03 18:46 ` Pavan Savoy
2010-05-04 14:03 ` Greg KH
2010-05-04 14:37 ` Pavan Savoy
2010-05-04 15:47 ` Greg KH [this message]
2010-05-04 15:52 ` Pavan Savoy
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=20100504154733.GA24636@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavan_savoy@yahoo.co.in \
--cc=tomas.winkler@intel.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 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.