linux-kernel - Re: [2.6.25-git18 => 2.6.26-rc1-git1] Xorg crash with xf86MapVidMem error

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 for Android: free password hash cracker in your pocket

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

Message-ID: <4823A059.1090400@zytor.com>
Date:	Thu, 08 May 2008 17:52:41 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Venki Pallipadi <venkatesh.pallipadi@...el.com>
CC:	Rufus & Azrael <rufus-azrael@...ericable.fr>,
	Ingo Molnar <mingo@...e.hu>,
	"Siddha, Suresh B" <suresh.b.siddha@...el.com>,
	Linux-kernel Mailing List <linux-kernel@...r.kernel.org>,
	Yinghai Lu <yhlu.kernel@...il.com>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [2.6.25-git18 => 2.6.26-rc1-git1] Xorg crash with	xf86MapVidMem
 error

Venki Pallipadi wrote:
> 
> One of the reason for heristic was to get proper type for /dev/mem maps for WB
> region (ACPI and BIOS area). /dev/mem checks to see the mtrr type of the start
> address and starts with that type for the request. As long as there are no
> other conflict in PAT list, we can give WB to this /dev/mem request. Not
> having this heuristic we will have to most probably default to UC.
> 
> When there are overlapping PAT list entries, the mtrr_lookup does not matter
> as we have to inherit things from those PAT entries or conflicting with them.
> 

Okay, now here is something...

I don't believe it is kosher for mmap() to behave differently if we 
called it once or called it twice.

Therefore, the proper behaviour in the case of a range that covers 
multiple types is to break it down into multiple requests each mapped 
with the appropriate type, as if mmap had been called separate on each 
subrange.  In the limiting case, yes, this does mean the subranges can 
be individual pages, but such an outcome is vanishingly improbable in 
practice.

	-hpa

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