From: Toshi Kani <toshi.kani@hpe.com>
To: mingo@kernel.org, bp@suse.de, hpa@zytor.com, tglx@linutronix.de
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
Toshi Kani <toshi.kani@hpe.com>,
"Luis R. Rodriguez" <mcgrof@suse.com>,
Andy Lutomirski <luto@kernel.org>,
Dan Williams <dan.j.williams@intel.com>
Subject: [PATCH] x86/mm: Add warning to ioremap() for conflicting cache type
Date: Wed, 27 Apr 2016 09:25:57 -0600 [thread overview]
Message-ID: <1461770757-26817-1-git-send-email-toshi.kani@hpe.com> (raw)
On x86, ioremap() and remap_pfn_range() fail on conflicting cache
type of an alias mapping request only if the case is not allowed
by the rule set in is_new_memtype_allowed(). While this exemption
is necessary for remap_pfn_range() called for /dev/mem mappings,
it is not necessary for ioremap(). Drivers should never call
ioremap() with a conflicting cache type. This exemption handling
may hide possible bugs in drivers.
Add a warning message to ioremap() when a conflicting cache type
is allowed by is_new_memtype_allowed(). This helps us identify
such usages in drivers.
There is no change in the behavior.
Link: https://lkml.org/lkml/2016/4/16/54
Signed-off-by: Toshi Kani <toshi.kani@hpe.com>
Cc: Ingo Molnar <mingo@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: "H. Peter Anvin" <hpa@zytor.com>
Cc: Borislav Petkov <bp@suse.de>
Cc: Luis R. Rodriguez <mcgrof@suse.com>
Cc: Andy Lutomirski <luto@kernel.org>
Cc: Dan Williams <dan.j.williams@intel.com>
---
arch/x86/mm/ioremap.c | 10 ++++++----
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/arch/x86/mm/ioremap.c b/arch/x86/mm/ioremap.c
index 0d8d53d..16c5887 100644
--- a/arch/x86/mm/ioremap.c
+++ b/arch/x86/mm/ioremap.c
@@ -138,14 +138,16 @@ static void __iomem *__ioremap_caller(resource_size_t phys_addr,
}
if (pcm != new_pcm) {
- if (!is_new_memtype_allowed(phys_addr, size, pcm, new_pcm)) {
- printk(KERN_ERR
- "ioremap error for 0x%llx-0x%llx, requested 0x%x, got 0x%x\n",
+ retval = is_new_memtype_allowed(phys_addr, size, pcm, new_pcm);
+ pr_err(
+ "ioremap %s for 0x%llx-0x%llx, requested 0x%x, got 0x%x\n",
+ retval ? "warning" : "error",
(unsigned long long)phys_addr,
(unsigned long long)(phys_addr + size),
pcm, new_pcm);
+ if (!retval)
goto err_free_memtype;
- }
+
pcm = new_pcm;
}
next reply other threads:[~2016-04-27 15:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-27 15:25 Toshi Kani [this message]
2016-05-24 23:33 ` Luis R. Rodriguez
2016-05-25 19:34 ` Kani, Toshimitsu
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=1461770757-26817-1-git-send-email-toshi.kani@hpe.com \
--to=toshi.kani@hpe.com \
--cc=bp@suse.de \
--cc=dan.j.williams@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mcgrof@suse.com \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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
all inboxes | Powered by JetHome®