On Wed, 2004-10-20 at 09:40, Ingo Molnar wrote: > > - scsi_error_handler() fix > > - device subsystem device_remove locking fix > > thanks, i've applied these. The block/loop.c assert reported by Rui > seems to be a similar problem too. Yep, it's all the same scheme. Most of the offending code uses MUTEX_LOCKED in an init function and plays the down, and up from a different context game, which triggers the deadlock/owner verify. Not hard to fix, but at some places it takes a bit, until you see the intention of the driver hacker. The most surprising one was in driver/base. I did not expect that new 2.5/6 code uses those tricks too. Fixes for aic7xxx and sym53c8xx_2 attached. tglx