linux-kernel - Re: [RFC PATCH 06/12] PAT 64b: Add 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]

Date:	Sat, 15 Dec 2007 00:19:11 +0100
From:	Andi Kleen <ak@....de>
To:	"Siddha, Suresh B" <suresh.b.siddha@...el.com>
Cc:	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Roland Dreier <rdreier@...co.com>,
	venkatesh.pallipadi@...el.com, torvalds@...ux-foundation.org,
	gregkh@...e.de, airlied@...net.ie, davej@...hat.com, mingo@...e.hu,
	tglx@...utronix.de, hpa@...or.com, akpm@...ux-foundation.org,
	arjan@...radead.org, jesse.barnes@...el.com,
	linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH 06/12] PAT 64b: Add ioremap_wc support

> For now, we don't track RAM pages using memattr infrastructure. This is because,
> memattr infrastructure is not enough. i.e., while the page is getting
> tracked using memattr infrastructure,

> potentially the page can get
> freed(a bug that we need to catch, to avoid attribute aliasing).

That would be a bug in the caller. But anybody who sets non standard
attributes should go through memattr first.

The only exception is /dev/mem -- not sure how to handle this best.
Perhaps only allow memattr for non memory for there. 

-Andi
--
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/