linux-kernel - Re: [Intel-gfx] [PATCH 2/2] drm: record monitor status in output_poll

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: <yun1v5sb2av.fsf@aiko.keithp.com>
Date:	Wed, 08 Dec 2010 09:30:00 -0800
From:	Keith Packard <keithp@...thp.com>
To:	Chris Wilson <chris@...is-wilson.co.uk>,
	Florian Mickler <florian@...kler.org>
Cc:	Dave Airlie <airlied@...hat.com>, intel-gfx@...ts.freedesktop.org,
	linux-kernel@...r.kernel.org, dri-devel@...ts.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 2/2] drm: record monitor status in output_poll_execute

On Wed, 08 Dec 2010 17:08:04 +0000, Chris Wilson <chris@...is-wilson.co.uk> wrote:
> On Wed, 8 Dec 2010 17:34:24 +0100, Florian Mickler <florian@...kler.org> wrote:
> > Does that mean that the kernel regression will not be
> > fixed/worked-around for old userspace? 
> 
> I think there is some confusion in that I believe there is more than one
> backlight bug at play here.

The kernel and user space fixes addressed the same  technical problem
(failing to note that mode setting turned on the devices), but the
symptoms that this caused were different; in kernel mode, the result
would be that monitors would be left turned on when user space asked
that they be turned off (and left pointing at random memory too, which
was amusing). I think that the backlight issue was caused by the
user-space bug though.

-- 
keith.packard@...el.com

Content of type "application/pgp-signature" skipped