From: "Jan Beulich" <jbeulich@novell.com>
To: "Ingo Molnar" <mingo@elte.hu>
Cc: <linux-kernel@vger.kernel.org>
Subject: x86: potential ioremap() issues
Date: Thu, 28 Feb 2008 12:59:19 +0000 [thread overview]
Message-ID: <47C6BE37.76E4.0078.0@novell.com> (raw)
Ingo,
with the new ioremap() implementation I see a couple of (potential)
issues:
- When ioremap_page_range() fails, remove_vm_area() is used rather
than vunmap() - I think this will cause a 'struct vm_struct' leak.
- While ioremap() continues to happily map RAM pages (with a bogus
[see below] WARN_ON_ONCE()), cacheability of the memory is not
being restored in iounmap().
- The check for RAM pages (except for the WARN_ON_ONCE())
continues to be applied only to lowmem pages.
- The WARN_ON_ONCE() itself is applied to the pfn after the
preceding loop finished, i.e. to a pfn that doesn't actually participate
in the operation. Shouldn't it be moved inside the loop?
Thanks for any clarification,
Jan
next reply other threads:[~2008-02-28 12:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-28 12:59 Jan Beulich [this message]
2008-02-28 13:24 ` x86: potential ioremap() issues Ingo Molnar
2008-02-28 14:30 ` Jan Beulich
2008-02-29 22:04 ` Oliver Pinter
2008-03-03 10:44 ` Ingo Molnar
2008-03-03 15:19 ` Oliver Pinter
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=47C6BE37.76E4.0078.0@novell.com \
--to=jbeulich@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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.