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] [day] [month] [year] [list]

Date:	Thu, 08 May 2008 14:42:29 -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:
> On Thu, May 08, 2008 at 01:08:01PM -0700, Rufus & Azrael wrote:
>>    Venki Pallipadi a ecrit :
>>    >
>>    > Use UC_MINUS in reserve_memtype call with -1, when MTRR lookup fails for
>>    any
>>    > reason.
>>    >
>>    > Change the logic in mtrr_type_lookup to just get the type from the start
>>    > address. Using start and end adddress is not right/complete as start and
>>    > end can be covered by different mtrr (where old code will fail) or
>>    > start and end can be in same mtrr, but still have some different
>>    > memory type region in between. Using only start is less restrictive and
>>    > deterministic.
>>    >
>>    > Signed-off-by: Venkatesh Pallipadi <venkatesh.pallipadi@...el.com>
>>    >
>>    > ---
>>    >  arch/x86/kernel/cpu/mtrr/generic.c |    7 ++-----
>>    >  arch/x86/mm/pat.c                  |    8 +-------
>>    >  2 files changed, 3 insertions(+), 12 deletions(-)
>>    >
>>
>>    Hi Venki,
>>
>>    Patch applied on 2.6.26-rc1-git5 and all works fine in X server with 
>>    CONFIG_X86_PAT=y.
>>
>>    See dmesg and mtrr files attached.
>>
> 
> Thanks for reporting the problem and testing the fix.
> ingo/thomas/hpa: Can you please pick up this patch. Fixes the PAT regression
> reported on this thread.

Hm...

I have *serious* concerns about this; this might paper over this 
particular problem, but it just isn't *correct*.

The fact that the range check is implemented incorrectly is not an 
excuse to just dump it and ignore the problem; it should be fixed instead.

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