https://bugzilla.kernel.org/show_bug.cgi?id=17361 Theodore Tso <tytso@xxxxxxx> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tytso@xxxxxxx --- Comment #14 from Theodore Tso <tytso@xxxxxxx> 2010-10-02 16:42:45 --- People may not be paying attention to this due to the subject line. Except for the initial bug report, none of the other stack traces have anything to do with ext4/jbd2. And in the initial ext4 trace, we see the complaint that we're calling might_sleep() in ext4_mark_inode_dirty(), in a code path where we are manifestly not taking any spinlocks. And in fact we don't see any spinlocks being taken at the point where the complaint is mode in ext4_mark_inode_dirty(). Yet preempt_count > 1. It looks to me like some unrelated piece of code is bumping preempt_count, and not decrementing it. Maybe in some code which is called from an interrupt handler, in some device driver? That might explain why you're getting failures all over the kernel. It may be worth closing this report, and opening several new ones, one for each failure, and make it clear this is not an ext4-related problem, since the subject line and component assigned for this bug is highly misleading. Including your kernel config would also be useful when you do that. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
