From: "Pali Rohár" <pali.rohar@gmail.com>
To: Michal Hocko <mhocko@suse.cz>
Cc: Hans de Goede <hdegoede@redhat.com>,
Darren Hart <dvhart@infradead.org>,
Ben Skeggs <bskeggs@redhat.com>,
Stuart Hayes <stuart_hayes@dell.com>,
Matthew Garrett <mjg@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
platform-driver-x86@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: Possible broken MM code in dell-laptop.c?
Date: Mon, 15 Jun 2015 23:27:59 +0200 [thread overview]
Message-ID: <201506152327.59907@pali> (raw)
In-Reply-To: <20150615211816.GC16138@dhcp22.suse.cz>
[-- Attachment #1: Type: Text/Plain, Size: 1182 bytes --]
On Monday 15 June 2015 23:18:16 Michal Hocko wrote:
> On Sun 14-06-15 11:05:07, Pali Rohár wrote:
> > Hello,
> >
> > in drivers/platform/x86/dell-laptop.c is this part of code:
> >
> > static int __init dell_init(void)
> > {
> > ...
> >
> > /*
> >
> > * Allocate buffer below 4GB for SMI data--only 32-bit physical
> > addr * is passed to SMI handler.
> > */
> >
> > bufferpage = alloc_page(GFP_KERNEL | GFP_DMA32);
>
> [...]
>
> > buffer = page_address(bufferpage);
>
> [...]
>
> > fail_rfkill:
> > free_page((unsigned long)bufferpage);
>
> This one should be __free_page because it consumes struct page* and
> it is the proper counter part for alloc_page. free_page, just to
> make it confusing, consumes an address which has to be translated to
> a struct page.
>
> I have no idea why the API has been done this way and yeah, it is
> really confusing.
>
> [...]
>
> > static void __exit dell_exit(void)
> > {
> > ...
> >
> > free_page((unsigned long)buffer);
So both, either:
free_page((unsigned long)buffer);
or
__free_page(bufferpage);
is correct?
--
Pali Rohár
pali.rohar@gmail.com
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2015-06-15 21:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-14 9:05 Possible broken MM code in dell-laptop.c? Pali Rohár
2015-06-15 20:36 ` Darren Hart
2015-06-15 20:42 ` Pali Rohár
2015-06-16 10:12 ` Pavel Machek
2015-06-15 21:18 ` Michal Hocko
2015-06-15 21:27 ` Pali Rohár [this message]
2015-06-16 6:33 ` Michal Hocko
2015-06-16 7:15 ` Pali Rohár
2015-06-16 7:43 ` Michal Hocko
2015-06-17 3:43 ` Darren Hart
2015-06-17 7:19 ` Michal Hocko
2015-06-18 21:14 ` Darren Hart
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=201506152327.59907@pali \
--to=pali.rohar@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bskeggs@redhat.com \
--cc=dvhart@infradead.org \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.cz \
--cc=mjg@redhat.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=stuart_hayes@dell.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;
as well as URLs for NNTP newsgroup(s).