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

Message-ID: <20101208173424.76ec4041@schatten.dmk.lab>
Date:	Wed, 8 Dec 2010 17:34:24 +0100
From:	Florian Mickler <florian@...kler.org>
To:	Keith Packard <keithp@...thp.com>
Cc:	Chris Wilson <chris@...is-wilson.co.uk>,
	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 Sun, 05 Dec 2010 13:08:18 -0800
Keith Packard <keithp@...thp.com> wrote:

> On Sun, 5 Dec 2010 13:27:43 +0100, Florian Mickler <florian@...kler.org> wrote:
> > On Fri, 26 Nov 2010 10:45:59 -0800
> > Keith Packard <keithp@...thp.com> wrote:
> > 
> > > In order to correctly report monitor connected status changes, the
> > > previous monitor status must be recorded in the connector->status
> > > value instead of being discarded.
> > > 
> > > Signed-off-by: Keith Packard <keithp@...thp.com>
> > 
> > Keith, am I right to assume that these address 
> > https://bugzilla.kernel.org/show_bug.cgi?id=22672
> > and probably:
> > https://bugzilla.kernel.org/show_bug.cgi?id=23472
> 
> Yes, this is part of the patch for that. The other piece is in the 2D
> driver which has a matching bug. That patch is already on master.
> 

Does that mean that the kernel regression will not be
fixed/worked-around for old userspace? 

Regards,
Flo
--
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/