Hello, On Mon, Oct 31, 2016 at 10:45:56AM -0600, Tejun Heo wrote: > Tracking the owners of mutexes and rwsems does help quite a bit. I > don't think it's as simple as inheriting io sleep state from the > current owner tho. The owner might be running or in a non-IO sleep > when others try to grab the mutex. It is an option to ignore those > cases but this would have a real possibility to lead to surprising > results in some corner cases. If we choose to propagate dynamically, > it becomes an a lot more complex problem and I don't think it'd be > justfiable. > > Unless there can be a simple enough and reliable solution, I think > it'd be better to stick with explicit marking. Just posted the fixed version for the first patch. Any more thoughts on this? Thanks. -- tejun -- 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
