From: Tomas Winkler <tomasw@gmail.com>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: David Woodhouse <dwmw2@infradead.org>,
dhowells@redhat.com, Greg KH <greg@kroah.com>,
Johannes Berg <johannes@sipsolutions.net>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
Emmanuel Grumbach <egrumbach@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: request_firmware API exhaust memory
Date: Wed, 28 Apr 2010 16:07:34 +0300 [thread overview]
Message-ID: <g2m1ba2fa241004280607n2e234e1dj1ea37cfb609f8787@mail.gmail.com> (raw)
In-Reply-To: <x2qac3eb2511004280123gd6143cd3ge641825089865172@mail.gmail.com>
On Wed, Apr 28, 2010 at 11:23 AM, Kay Sievers <kay.sievers@vrfy.org> wrote:
> On Tue, Apr 27, 2010 at 15:34, Kay Sievers <kay.sievers@vrfy.org> wrote:
>> On Tue, Apr 27, 2010 at 14:43, David Woodhouse <dwmw2@infradead.org> wrote:
>>> This untested patch attempts to put the page array into the 'struct
>>> firmware' so that we can free it from release_firmware().
>>
>> Looks good. Seems to work without problems and without leaking memory.
>>
>> Misses only the member in the struct firmware though. :)
>
> Thomas, any chance to test David's patch, if that solves the issues you've seen?
>
> Just add the missing line:
>
> --- a/include/linux/firmware.h
> +++ b/include/linux/firmware.h
> @@ -12,6 +12,7 @@
> struct firmware {
> size_t size;
> const u8 *data;
> + struct page **pages;
> };
>
>
In progress. Will post results later today (timezone:GMT+2)
Thanks
Tomas
prev parent reply other threads:[~2010-04-28 13:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-19 12:20 Tomas Winkler
2010-04-19 12:35 ` Kay Sievers
2010-04-19 14:59 ` Greg KH
2010-04-21 22:22 ` Tomas Winkler
2010-04-25 16:37 ` Greg KH
2010-04-25 19:22 ` Tomas Winkler
2010-04-25 19:36 ` Greg KH
2010-04-25 20:09 ` Tomas Winkler
2010-04-26 10:38 ` Kay Sievers
2010-04-26 15:19 ` Kay Sievers
2010-04-26 16:59 ` Tomas Winkler
2010-04-27 4:12 ` Sujith Manoharan
2010-04-27 11:18 ` Tomas Winkler
2010-04-27 11:53 ` Tomas Winkler
2010-04-27 12:05 ` Kay Sievers
2010-04-27 12:43 ` David Woodhouse
2010-04-27 13:34 ` Kay Sievers
2010-04-28 8:23 ` Kay Sievers
2010-04-28 13:07 ` Tomas Winkler [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=g2m1ba2fa241004280607n2e234e1dj1ea37cfb609f8787@mail.gmail.com \
--to=tomasw@gmail.com \
--cc=dhowells@redhat.com \
--cc=dwmw2@infradead.org \
--cc=egrumbach@gmail.com \
--cc=greg@kroah.com \
--cc=johannes@sipsolutions.net \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
/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
all inboxes | Powered by JetHome®