On Mon, 5 Nov 2012, Alan Cox wrote: > > The fbdev potential for deadlock may be years old, but the warning > > (and consequent disabling of lockdep from that point on - making it > > useless to everybody else in need of it) is new, and comes from the > > commit below in linux-next. > > > > I revert it in my own testing: if there is no quick fix to the > > fbdev issue on the way, Daniel, please revert it from your tree. > > If you revert it you swap it for a different deadlock - and one that > happens more often I would expect. Not very useful.
But a deadlock we have lived with for years. Without reverting, we're prevented from discovering all the new deadlocks we're adding. > > I'm hoping the framebuffer maintainer will bother to respond to this > because that's the only way it can be sorted out. That would be ideal - thanks. Hugh -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
