On 2010-10-02, at 09:42, Theodore Tso <tytso@xxxxxxx> wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=17361 > > 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. In my experience, this is typically caused by stack overflow smashing the task struct and randomly setting preempt_count to a non-zero value. Cheers, Andreas -- 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
