Hi Greg,
On Thu, Sep 27, 2018 at 9:56 PM, Sudip Mukherjee
<sudipm.mukherjee@xxxxxxxxx> wrote:
> Hi Greg,
>
> On Thu, Sep 27, 2018 at 10:03 AM, Greg Kroah-Hartman
> <gregkh@xxxxxxxxxxxxxxxxxxx> wrote:
>> This is the start of the stable review cycle for the 4.14.73 release.
>> There are 64 patches in this series, all will be posted as a response
>> to this one. If anyone has any issues with these being applied, please
>> let me know.
>>
>> Responses should be made by Sat Sep 29 09:02:21 UTC 2018.
>> Anything received after that time might be too late.
>
> My kvm guest had this:
>
<snip>
> [ 8.585076] RIP: drm_debugfs_init+0x183/0x370 [drm] RSP: ffff88002b1bf5e8
> [ 8.585404] ---[ end trace 62728db3ac408aba ]---
>
> And I had to revert 7e58fe2a97bc ("drm/atomic: Use
> drm_drv_uses_atomic_modeset() for debugfs creation") to make it work.
> I am looking more into why it failed.
update:
Backporting 57078338b2e4 ("drm: fix drm_drv_uses_atomic_modeset on non
modesetting drivers.") fixed the issue. But 7e58fe2a97bc ("drm/atomic:
Use drm_drv_uses_atomic_modeset() for debugfs creation") changed the
functionality of the check. If this has to be applied, it will also
need an additional patch to keep the check same as linus tree.
But looking at the other mails now, and you have already dropped the patch.
--
Regards
Sudip
