mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Yinghai Lu" <yhlu.kernel@gmail.com>
To: "Jeremy Fitzhardinge" <jeremy@goop.org>
Cc: "Ingo Molnar" <mingo@elte.hu>,
	linux-kernel@vger.kernel.org,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH 6 of 7] x86: use early_ioremap in __acpi_map_table
Date: Thu, 11 Sep 2008 13:34:12 -0700	[thread overview]
Message-ID: <86802c440809111334u6d6691c3sd83bcfddc83b1bbd@mail.gmail.com> (raw)
In-Reply-To: <48C7FA91.9050302@goop.org>

On Wed, Sep 10, 2008 at 9:49 AM, Jeremy Fitzhardinge <jeremy@goop.org> wrote:
> Ingo Molnar wrote:
>>> So i'd suggest a different, more carful approach: keep the new code
>>> you wrote, but print a WARN()ing if prev_map is not unmapped yet when
>>> the next mapping is acquired. That way the ACPI code can be fixed
>>> gradually and without breaking existing functionality.
>>>
>>
>> ok, i stuck in your patches into tip/master today and -tip testing
>> quickly found an early-ioremap leak:
>>
>> [   36.625100] calling  check_early_ioremap_leak+0x0/0x3d
>> [   36.630253] ------------[ cut here ]------------
>> [   36.634884] WARNING: at arch/x86/mm/ioremap.c:577 check_early_ioremap_leak+0x28/0x3d()
>> [   36.642811] Debug warning: early ioremap leak of 1 areas detected.
>>
>> find the full log below with ioremap-leak-tracing turned on. I've
>> excluded these commits for now from tip/master.
>>
>
> Yes, that leak is expected, unfortunately.  __acpi_map_table() has no
> corresponding unmap, and only maintains one mapping.  So it will leak
> its last mapping when it switches over from using __acpi_map_table() to
> ioremap().
>
> So, yes, its ugly, but its guaranteed to be a single leaked mapping.
> But I'm not sure what the best approach to deal with it is.
>
> (All those other backtraces are just informational, right?)
>

acpi_os_map_memory is the only user for __acpi_map_table (except es7000_32.c)

void __iomem *__init_refok
acpi_os_map_memory(acpi_physical_address phys, acpi_size size)
{
        if (phys > ULONG_MAX) {
                printk(KERN_ERR PREFIX "Cannot map memory that high\n");
                return NULL;
        }
        if (acpi_gbl_permanent_mmap)
                /*
                * ioremap checks to ensure this is in reserved space
                */
                return ioremap((unsigned long)phys, size);
        else
                return __acpi_map_table((unsigned long)phys, size);
}
EXPORT_SYMBOL_GPL(acpi_os_map_memory);

void acpi_os_unmap_memory(void __iomem * virt, acpi_size size)
{
        if (acpi_gbl_permanent_mmap) {
                iounmap(virt);
        }
}
EXPORT_SYMBOL_GPL(acpi_os_unmap_memory);

just let acpi_os_unmap_memory to call __acpi_unmap_table...

YH

  parent reply	other threads:[~2008-09-11 20:34 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-07 22:21 [PATCH 0 of 7] x86: lay groundwork for Xen domain 0 support Jeremy Fitzhardinge
2008-09-07 22:21 ` [PATCH 1 of 7] x86: add _PAGE_IOMAP pte flag for IO mappings Jeremy Fitzhardinge
2008-09-09 13:32   ` Avi Kivity
2008-09-09 14:47     ` Jeremy Fitzhardinge
2008-09-09 14:56       ` Avi Kivity
2008-09-09 15:29         ` [Xen-devel] " Keir Fraser
2008-09-09 15:48           ` Jeremy Fitzhardinge
2008-09-09 16:05             ` Keir Fraser
2008-09-10  9:55         ` Avi Kivity
2008-09-10 16:38           ` Jeremy Fitzhardinge
2008-09-10 16:55             ` Nick Piggin
2008-09-10 17:27               ` Jeremy Fitzhardinge
2008-09-07 22:21 ` [PATCH 2 of 7] x86: remove duplicate early_ioremap declarations Jeremy Fitzhardinge
2008-09-07 22:21 ` [PATCH 3 of 7] x86: add early_memremap() Jeremy Fitzhardinge
2008-09-07 22:21 ` [PATCH 4 of 7] x86: use early_memremap() in setup.c Jeremy Fitzhardinge
2008-09-07 22:21 ` [PATCH 5 of 7] x86-64: don't check for map replacement Jeremy Fitzhardinge
2008-09-07 22:21 ` [PATCH 6 of 7] x86: use early_ioremap in __acpi_map_table Jeremy Fitzhardinge
2008-09-07 23:44   ` Andi Kleen
2008-09-08  0:03     ` Jeremy Fitzhardinge
2008-09-08 14:26       ` Ingo Molnar
2008-09-08 16:29         ` Jeremy Fitzhardinge
2008-09-08 19:41         ` Jeremy Fitzhardinge
2008-09-10 11:55         ` Ingo Molnar
2008-09-10 16:49           ` Jeremy Fitzhardinge
2008-09-11  7:33             ` Ingo Molnar
2008-09-11 18:36               ` Jeremy Fitzhardinge
2008-09-11 18:56                 ` Ingo Molnar
2008-09-11 20:34             ` Yinghai Lu [this message]
2008-09-11 21:07               ` Jeremy Fitzhardinge
2008-09-12  9:49                 ` Ingo Molnar
2008-09-12 17:31                   ` Yinghai Lu
     [not found]             ` <20080911125748.GA14698@elte.hu>
2008-09-11 21:33               ` [PATCH] acpi: remove final __acpi_map_table mapping before setting acpi_gbl_permanent_mmap Jeremy Fitzhardinge
2008-09-07 22:21 ` [PATCH 7 of 7] x86: always explicitly map acpi memory Jeremy Fitzhardinge
2008-09-07 23:35   ` [Xen-devel] " Yinghai Lu
2008-09-08  0:02     ` Jeremy Fitzhardinge
2008-09-08  0:14       ` Yinghai Lu

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=86802c440809111334u6d6691c3sd83bcfddc83b1bbd@mail.gmail.com \
    --to=yhlu.kernel@gmail.com \
    --cc=hpa@zytor.com \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    /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

Powered by JetHome