On Fri, Jul 10, 2015 at 5:02 PM, Jeff Layton <jeff.layton@xxxxxxxxxxxxxxx> wrote: > So, William has done some testing and hit some problems with this > patch. I suspect that it's because we can end up running an unlock > after the filp->f_count has already gone to zero and are in __fput, so > we take an extra reference and end up with a use-after-free. > > I think it'd be best to revert this patch from all kernels for now > (mainline and stable). I don't think the one that changes the setlk > codepath is susceptible to this, but it's probably fine to hold off on > applying both until I can sort out a better way to fix this one. I also think it's safer to revert both of them. -- William -- 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