linux-kernel - Re: [BUG] drm/i915 Screen corruption introduced by a00b10c360b35d6431a94cb

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

Message-ID: <96f4040e154c151ce996b4afdaf42d5f.squirrel@webmail.greenhost.nl>
Date:	Tue, 22 Feb 2011 04:39:55 +0100 (CET)
From:	"Indan Zupancic" <indan@....nu>
To:	"Indan Zupancic" <indan@....nu>
Cc:	"Chris Wilson" <chris@...is-wilson.co.uk>,
	"LKML" <linux-kernel@...r.kernel.org>,
	dri-devel@...ts.freedesktop.org
Subject: Re: [BUG] drm/i915 Screen corruption introduced by      
     a00b10c360b35d6431a94cb

On Tue, February 22, 2011 04:25, Indan Zupancic wrote:
> Hi,
>
> On Sun, February 20, 2011 14:21, Daniel Vetter wrote:
>> Well, don't start jumping around, yet. These patches are just to rule out
>> some theories. Now: Is it fixed with just the 2nd patch alone or do you need both
>> patches? This is very important, so please test extensively whether there are really
>> no corruptions with just the 2nd patch.
>
> I managed to create some corruption with an xterm above xpdf. It looks  different
> than the original corruption, so I think it's safe to say it's a different bug:
>
> http://img593.imageshack.us/i/ss1298340823.png
> http://img203.imageshack.us/i/ss1298340776.png
>
> This was without xcompmgr running, I don't think I would have seen it otherwise.
> Actually, it turns out it's really easy to trigger as well, so I can more easily
> test patches now. Unfortunately I wasn't smart enough to store the bisecting kernels,
> gah!
>
> I tried with both your patches, as well as the HIC poking patch, but I still get it.
>
> I'll try to pinpoint more exactly when this started to happen.

Okay, I tried older kernels and I get it even with 2.6.34, so I think it's a bug
in userspace, like intel-dri, or perhaps the intel X driver (though I get the same
with an older version).

Greetings,

Indan


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