[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <ActXXBRCAJY1WXkb1rRkIIdrHBvij0nuYv61GfTkwduOvS-mmb2jOAFmwxq0UPOZeZFXxWIhkOZBgYPSUFxKdGgxmYcPVBUk8IF6PodWFg8=@emersion.fr>
Date: Mon, 14 Oct 2019 09:22:12 +0000
From: Simon Ser <contact@...rsion.fr>
To: Daniel Vetter <daniel@...ll.ch>
Cc: syzbot <syzbot+e7ad70d406e74d8fc9d0@...kaller.appspotmail.com>,
"hamohammed.sa@...il.com" <hamohammed.sa@...il.com>,
"rodrigosiqueiramelo@...il.com" <rodrigosiqueiramelo@...il.com>,
"airlied@...ux.ie" <airlied@...ux.ie>,
"syzkaller-bugs@...glegroups.com" <syzkaller-bugs@...glegroups.com>,
"oleg.vasilev@...el.com" <oleg.vasilev@...el.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>,
"simon.ser@...el.com" <simon.ser@...el.com>,
"omrigann@...il.com" <omrigann@...il.com>
Subject: Re: WARNING in vkms_gem_free_object
On Monday, October 14, 2019 12:17 PM, Daniel Vetter <daniel@...ll.ch> wrote:
> Oleg, will you be looking at this? With the reproducer and full drm
> debugging enabled it shouldn't be too hard to figure out what's going on
> heere ...
Oleg is no longer working at Intel. I don't think he monitors dri-devel
anymore.
I'd like to work on VKMS myself, but it's very unlikely I have time to
do so anytime soon.
(Neither Oleg nor I have access to our @intel.com address anymore.)
Powered by blists - more mailing lists