All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Pali Rohár" <pali.rohar@gmail.com>
To: 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>,
	Michal Hocko <mhocko@suse.cz>
Cc: platform-driver-x86@vger.kernel.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Possible broken MM code in dell-laptop.c?
Date: Sun, 14 Jun 2015 11:05:07 +0200	[thread overview]
Message-ID: <201506141105.07171@pali> (raw)

[-- Attachment #1: Type: text/plain, Size: 1919 bytes --]

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 suspect that there is some problem with free_page() call. In dell_init 
is called free_page() on bufferpage and in dell_exit() on buffer.

Matthew and Stuart, you introduced this inconsistency in commit:

-------------------------------------------------
commit 116ee77b2858d9c89c0327f3a47c8ba864bf4a96
Author: Stuart Hayes <stuart_hayes@dell.com>
Committer: Matthew Garrett <mjg@redhat.com>
Date:   Wed Feb 10 14:12:13 2010 -0500

    dell-laptop: Use buffer with 32-bit physical address

    Calls to communicate with system firmware via a SMI (using dcdbas)
    need to use a buffer that has a physical address of 4GB or less.
    Currently the dell-laptop driver does not guarantee this, and when 
the
    buffer address is higher than 4GB, the address is truncated to 32 
bits
    and the SMI handler writes to the wrong memory address.
    
    Signed-off-by: Stuart Hayes <stuart_hayes@dell.com>
    Acked-by: Matthew Garrett <mjg@redhat.com>
-------------------------------------------------

Can you or somebody else (CCed linux-mm) look at this page related code? 
I think it is wrong, but somebody authoritative should provide answer.

Thanks.

-- 
Pali Rohár
pali.rohar@gmail.com

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

             reply	other threads:[~2015-06-14  9:05 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-14  9:05 Pali Rohár [this message]
2015-06-15 20:36 ` Possible broken MM code in dell-laptop.c? Darren Hart
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=201506141105.07171@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 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.