On Tue, Jan 29, 2013 at 12:22 PM, Nicholas A. Bellinger <nab@xxxxxxxxxxxxxxx> wrote: > > However, AFAICT with my v3.8-rc2 setup (which does have a bunch of > kernel debugging enabled), calling cancel_work_sync() on an > uninitialized cmd->work does not trigger a similar OOPs to what you've > reported. Right, that's the part I'm a bit mystified by. I've seen lockdep warnings because of this, but I'm not sure why it might crash. Christopher, could you send the output of "objdump -S kernel/workqueue.o" so I can try and figure out where exactly in __cancel_work_timer() you're crashing? It's probably pretty big so feel free to send just to me off-list. - R. -- To unsubscribe from this list: send the line "unsubscribe target-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
