All of lore.kernel.org
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@infradead.org>
To: "Pali Rohár" <pali.rohar@gmail.com>
Cc: 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: Mon, 15 Jun 2015 13:36:45 -0700	[thread overview]
Message-ID: <20150615203645.GD83198@vmdeb7> (raw)
In-Reply-To: <201506141105.07171@pali>

On Sun, Jun 14, 2015 at 11:05:07AM +0200, 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);
> 	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?

-- 
Darren Hart
Intel Open Source Technology Center

WARNING: multiple messages have this Message-ID (diff)
From: Darren Hart <dvhart@infradead.org>
To: "Pali Rohár" <pali.rohar@gmail.com>
Cc: 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: Mon, 15 Jun 2015 13:36:45 -0700	[thread overview]
Message-ID: <20150615203645.GD83198@vmdeb7> (raw)
In-Reply-To: <201506141105.07171@pali>

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?

-- 
Darren Hart
Intel Open Source Technology Center

--
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>

  reply	other threads:[~2015-06-15 20:36 UTC|newest]

Thread overview: 22+ 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 [this message]
2015-06-15 20:36   ` Darren Hart
2015-06-15 20:42   ` Pali Rohár
2015-06-16 10:12     ` Pavel Machek
2015-06-16 10:12       ` Pavel Machek
2015-06-15 21:18 ` Michal Hocko
2015-06-15 21:18   ` Michal Hocko
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  6:33       ` Michal Hocko
2015-06-16  7:15       ` Pali Rohár
2015-06-16  7:15         ` Pali Rohár
2015-06-16  7:43         ` Michal Hocko
2015-06-16  7:43           ` Michal Hocko
2015-06-17  3:43         ` Darren Hart
2015-06-17  3:43           ` Darren Hart
2015-06-17  7:19           ` Michal Hocko
2015-06-17  7:19             ` Michal Hocko
2015-06-18 21:14             ` Darren Hart
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=20150615203645.GD83198@vmdeb7 \
    --to=dvhart@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=bskeggs@redhat.com \
    --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 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.