linux-kernel - Re: [patch] x86, voyager: fix ioremap

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20080427.155834.189904598.davem@davemloft.net>
Date:	Sun, 27 Apr 2008 15:58:34 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	hpa@...or.com
Cc:	jeff@...zik.org, James.Bottomley@...senPartnership.com,
	mingo@...e.hu, tglx@...utronix.de, linux-kernel@...r.kernel.org,
	torvalds@...ux-foundation.org
Subject: Re: [patch] x86, voyager: fix ioremap_nocache()

From: "H. Peter Anvin" <hpa@...or.com>
Date: Sun, 27 Apr 2008 15:52:02 -0700

> Arguably, the right thing is to not even have ioremap() anymore, just 
> ioremap_{cache,nocache,wc} and consider any unconverted ioremap() as a 
> flag to audit that particular piece of code.
> 
> I don't think that can be done "instantly", though, so defaulting 
> ioremap() to uncached (as it apparently has been on other arches 
> already?) is the conservative option in the meantime.

I think this is a reasonable course of action.

That leaves one of Jeff's concerns, what to do with pci_iomap().  That
was designed to give mappings with caching enabled, and as a result we
probably should make it behave that way.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/