From: Pavel Machek <pavel@ucw.cz>
To: "Pali Rohár" <pali.rohar@gmail.com>
Cc: Darren Hart <dvhart@infradead.org>,
Hans de Goede <hdegoede@redhat.com>,
Ben Skeggs <bskeggs@redhat.com>,
Stuart Hayes <stuart_hayes@dell.com>,
Matthew Garrett <mjg@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Michal Hocko <mhocko@suse.cz>,
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: Tue, 16 Jun 2015 12:12:12 +0200 [thread overview]
Message-ID: <20150616101211.GA25899@amd> (raw)
In-Reply-To: <201506152242.30732@pali>
On Mon 2015-06-15 22:42:30, Pali Rohar wrote:
> On Monday 15 June 2015 22:36:45 Darren Hart wrote:
> > On Sun, Jun 14, 2015 at 11:05:07AM +0200, Pali Rohar 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);
> > > if (!bufferpage) {
> > >
> > > ret = -ENOMEM;
> > > goto fail_buffer;
> > >
> > > }
> > > buffer = page_address(bufferpage);
> > >
> > > ret = dell_setup_rfkill();
> > >
> > > if (ret) {
> > >
> > > pr_warn("Unable to setup rfkill\n");
> > > goto fail_rfkill;
> > >
> > > }
> > >
> > > ...
> > >
> > > fail_rfkill:
> > > free_page((unsigned long)bufferpage);
> > >
> > > fail_buffer:
> > > ...
> > > }
> > >
> > > Then there is another part:
> > >
> > > static void __exit dell_exit(void)
> > > {
> > > ...
> > >
> > > free_page((unsigned long)buffer);
> >
> > I believe you are correct, and this should be bufferpage. Have you
> > observed any failures?
>
> Rmmoding dell-laptop.ko works fine. There is no error in dmesg. I think
> that buffer (and not bufferpage) should be passed to free_page(). So in
> my opinion problem is at fail_rfkill: label and not in dell_exit().
You seem to be right. Interface is strange...
alloc_pages() returns struct page *,
__free_pages() takes struct page *,
free_pages() takes unsinged long.
Best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2015-06-16 10:12 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 [this message]
2015-06-15 21:18 ` Michal Hocko
2015-06-15 21:27 ` Pali Rohár
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=20150616101211.GA25899@amd \
--to=pavel@ucw.cz \
--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=pali.rohar@gmail.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).