[Bug 71208] [regression] module_reload segfault
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Tue Nov 12 23:08:48 PST 2013
https://bugs.freedesktop.org/show_bug.cgi?id=71208
lu hua <huax.lu at intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |REOPENED
--- Comment #5 from lu hua <huax.lu at intel.com> ---
(In reply to comment #2)
> Created attachment 88992 [details]
> dmesg
>
> Test on latest -nightly branch. It still fails on -nightly branch.
> output:
> ./drv_module_reload: line 27: 3995 Killed rmmod i915
> WARNING: i915.ko still loaded!
> ./drv_module_reload: line 43: /sys/class/vtconsole/vtcon1/bind: No such file
> or directory
>
Bisect shows: 8f6599da8e772fa8de54cdf98e9e03cbaf3946da is the first bad commit.
commit 8f6599da8e772fa8de54cdf98e9e03cbaf3946da
Author: David Herrmann <dh.herrmann at gmail.com>
AuthorDate: Sun Oct 20 18:55:45 2013 +0200
Commit: Dave Airlie <airlied at redhat.com>
CommitDate: Wed Nov 6 14:53:25 2013 +1000
drm: delay minor destruction to drm_dev_free()
Instead of freeing minors in drm_dev_unregister(), we only unplug them and
delay the free to drm_dev_free(). Note that if drm_dev_register() has
never been called, minors are NULL and this has no effect.
This change is needed to allow early device unregistration. If we want to
call drm_dev_unregister() on live devices, we need to guarantee that
minors are still valid (but unplugged). This way, any open file can still
access file_priv->minor->dev to get the DRM device. However, the minor is
unplugged so no new users can occur.
Signed-off-by: David Herrmann <dh.herrmann at gmail.com>
Signed-off-by: Dave Airlie <airlied at redhat.com>
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20131113/c361fc81/attachment.html>
More information about the intel-gfx-bugs
mailing list