This is a note to let you know that I've just added the patch titled

    drm: don't check modeset locks in panic handler

to the 3.0-stable tree which can be found at:
    
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary

The filename of the patch is:
     drm-don-t-check-modeset-locks-in-panic-handler.patch
and it can be found in the queue-3.0 subdirectory.

If you, or anyone else, feels it should not be added to the stable tree,
please let <[email protected]> know about it.


>From a9b054e8ab06504c2afa0e307ee78d3778993a1d Mon Sep 17 00:00:00 2001
From: Daniel Vetter <[email protected]>
Date: Thu, 2 May 2013 09:43:05 +0200
Subject: drm: don't check modeset locks in panic handler

From: Daniel Vetter <[email protected]>

commit a9b054e8ab06504c2afa0e307ee78d3778993a1d upstream.

Since we know that locking is broken in that case and it's more
important to not flood the dmesg with random gunk.

References: http://lkml.kernel.org/r/[email protected]
Cc: Dave Airlie <[email protected]>
Cc: Borislav Petkov <[email protected]>
Reported-and-tested-by: Borislav Petkov <[email protected]>
Signed-off-by: Daniel Vetter <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>

---
 drivers/gpu/drm/drm_crtc.c |    4 ++++
 1 file changed, 4 insertions(+)

--- a/drivers/gpu/drm/drm_crtc.c
+++ b/drivers/gpu/drm/drm_crtc.c
@@ -907,6 +907,10 @@ int drm_mode_group_init_legacy_group(str
        if ((ret = drm_mode_group_init(dev, group)))
                return ret;
 
+       /* Locking is currently fubar in the panic handler. */
+       if (oops_in_progress)
+               return;
+
        list_for_each_entry(crtc, &dev->mode_config.crtc_list, head)
                group->id_list[group->num_crtcs++] = crtc->base.id;
 


Patches currently in stable-queue which might be from [email protected] are

queue-3.0/drm-mm-fix-dump-table-bug.patch
queue-3.0/drm-don-t-check-modeset-locks-in-panic-handler.patch
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to