linux-kernel - Re: [Bug 10843] Display artifacts on XOrg logout with PAT kernel and VESA framebuffer

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: <200809131149.55472.elendil@planet.nl>
Date:	Sat, 13 Sep 2008 11:49:54 +0200
From:	Frans Pop <elendil@...net.nl>
To:	"Pallipadi, Venkatesh" <venkatesh.pallipadi@...el.com>
Cc:	"Siddha, Suresh B" <suresh.b.siddha@...el.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Ingo Molnar <mingo@...e.hu>,
	"arjan@...ux.intel.com" <arjan@...ux.intel.com>,
	"jbarnes@...tuousgeek.org" <jbarnes@...tuousgeek.org>
Subject: Re: [Bug 10843] Display artifacts on XOrg logout with PAT kernel and VESA framebuffer

On Saturday 13 September 2008, Pallipadi, Venkatesh wrote:
> >We have too many entires in PAT list due to RAM pages being marked
> >UC by drivers. Unfortunately, there are no quick fixes that can fix
> >this for 2.6.27. However, we are aware of the problem here and
> >working on a more complete fix for this. We should have the patch
> >for it soon.
>
> Can you try the patch here
> http://www.ussg.iu.edu/hypermail/linux/kernel/0809.1/2074.html
> And report back whether that resolves the issue.

Yes, that solves the issue. The display is now free of artifacts again, 
both on logout and when I switch users in X.
The pat_memtype_list looks a lot more sane too (see attachment).

So it _was_ a regression caused by pat itself after all, and not the 
result of incorrect memory handling in the framebuffer code.
Could you take over the bug report #10843 in bugzilla (it is currently 
assigned to the framebuffer people) and ensure it gets closed once the 
patch gets accepted in Linus' tree?

I'm glad you were able to get this sorted out.

Feel free to add my:
Tested-by: Frans Pop <elendil@...net.nl>

Thanks,
FJP

View attachment "pat_memtype_list" of type "text/plain" (1228 bytes)