Hi Ingo, I was wondering if the issue the bit_spin_lock has gone into the side burner? I understand that this is a major problem to change it, if you want to get into the mainline kernel. But I still believe it to be a problem. With kjournald spinning on a bit lock until it finishes it's quota, can be bad for latencies.
Although it only deadlocks on your system if it was a real-time task, it still has the ability to become one. Since it can hold two different locks at the time of the spin, if a rt-task tries to grab it, with priority inheritance it becomes rt, and if that just happened to be the highest priority task on the system, you just created a deadlock. It's not so much of an issue with me, since I'm working with a parallel kernel, and have implemented my earlier fixes to it. I just wanted to know if there's any plan to deal with them on your end. I do see this causing a random lockup once in a while, and wanted the user to beware. Of course if you just avoid ext3, you wont have a problem. -- Steve - 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/
