On Thu, Dec 05, 2013 at 11:09:02AM +0100, Mateusz Guzik wrote: > Commit 36f5588905c10a8c4568a210d601fe8c3c27e0f0 > "aio: refcounting cleanup" resulted in ioctx_lock not being held > during ctx removal, leaving the list susceptible to corruptions. > > In mainline kernel the issue went away as a side effect of > db446a08c23d5475e6b08c87acca79ebb20f283c "aio: convert the ioctx list to > table lookup v3". > > Fix the problem by restoring appropriate locking. Why can't I just take db446a08c23d5475e6b08c87acca79ebb20f283c instead? Does it not work well enough, or is there other issues involved in it that would keep it out of stable? Also, it seems like the performance increase of that patch would be good to have backported, right? thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html