linux-kernel - Re: v4.14.21+: ATOMIC_SLEEP splat bisected to 9428088c90b6 ("drm/qxl: reapply cursor after resetting primary")

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, 17 Jun 2018 11:36:07 +0200
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Mike Galbraith <efault@....de>
Cc:     Ray Strode <rstrode@...hat.com>,
        LKML <linux-kernel@...r.kernel.org>,
        stable <stable@...r.kernel.org>,
        Gerd Hoffmann <kraxel@...hat.com>,
        Dave Airlie <airlied@...hat.com>,
        virtualization@...ts.linux-foundation.org
Subject: Re: v4.14.21+: ATOMIC_SLEEP splat bisected  to 9428088c90b6
 ("drm/qxl: reapply cursor after resetting primary")

On Sat, Jun 16, 2018 at 05:39:11PM +0200, Mike Galbraith wrote:
> Greetings,
> 
> Running a kernel with ATOMIC_SLEEP enabled in one of my VMs, I met the
> splat below.  I tracked it back to 4.14-stable, and bisected it there.

Why does your virtual machine use a drm driver?  Ah, it's a driver for
virtual gpu, nice.

And if you revert that patch, does everything work again?

> # first bad commit: [848dd9bf51544c8e5436960124f3d1f9c51cdb99] drm/qxl: reapply cursor after resetting primary

You should also cc: the other developers on that signed-off-by list,
like I did here...

thanks,

greg k-h