Hello, Cornelia Huck wrote: > ======================================================= > [ INFO: possible circular locking dependency detected ] > 2.6.21-rc6-ge666c753-dirty #54 > ------------------------------------------------------- > kslowcrw/64 is trying to acquire lock: > (&sch->reg_mutex){--..}, at: [<00000000004233b2>] mutex_lock+0x3e/0x4c > > but task is already holding lock: > (&sd->s_active){----}, at: [<0000000000209578>] remove_dir+0xec/0x144 > > which lock already depends on the new lock.
This is probably because s_active has different write locked and unlocked by different threads but it doesn't tell lockdep about it. I'll read lockdep docs and update it. Thanks for testing. -- tejun - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/