linux-kernel - Re: [PATCH 3.14 42/79] drm/qxl: only report first monitor as connected if we have no state

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]

Date:	Sun, 14 Aug 2016 16:51:46 +0200
From:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:	Jiri Slaby <jslaby@...e.cz>
Cc:	linux-kernel@...r.kernel.org, stable@...r.kernel.org,
	Dave Airlie <airlied@...hat.com>
Subject: Re: [PATCH 3.14 42/79] drm/qxl: only report first monitor as
 connected if we have no state

On Fri, May 27, 2016 at 01:06:24PM +0200, Jiri Slaby wrote:
> On 10/18/2015, 04:05 AM, Greg Kroah-Hartman wrote:
> > 3.14-stable review patch.  If anyone has any objections, please let me know.
> > 
> > ------------------
> > 
> > From: Dave Airlie <airlied@...hat.com>
> > 
> > commit 69e5d3f893e19613486f300fd6e631810338aa4b upstream.
> > 
> > If the server isn't new enough to give us state, report the first
> > monitor as always connected, otherwise believe the server side.
> 
> Hi,
> 
> I've got a bug report, that this commit breaks 3.12-stable:
> ===============
> While testing KDE5 packages which will be landing in Package Hub for
> SP1, we found a issue with qxl drm driver in kernel.
> 
> When booting SLES (or SLED) 12 SP1, in a libvirt KVM environment, with
> QXL as video driver, KDE5 plasma was not rendered on screen, you could
> only see mouse cursor.
> 
> Booting with nomodeset=1 or qxl.modeset=0 fixes the issue.
> ===============
> 
> Does it make sense? Is 3.12 missing some prerequisite? Or should we just
> revert the commit in 3.12? And what about 3.14, 4.1?

What ever happened to this?  Did you revert this in 3.12-stable?

thanks,

greg k-h