On Fri, 2007-07-13 at 14:47 -0700, Zach Brown wrote: > Peter, do you have any interest in seeing how far we can get > at tracking lock_page()? I'm not holding my breath, but any little bit > would probably help. I ran headfirst into the fact the unlock_page() need not be called by the same task that did lock_page(). Esp IO-completion interrupts love to unlock pages they did not lock themselves. Not at all sure that is fixable, it seems to be the nature of the async structure of the problem :-( - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
