Hi Andrew, Here's my latest and hopefully last stab at fixing the trinity hole-punch starvation issue that became known as CVE-2014-4171. You may prefer to hear a testing update from Sasha and Vlastimil before paying any attention to these, or you may prefer to add them into mmotm for wider testing now: whichever you think appropriate. Please throw away mmotm's revert-shmem-fix-faulting-into-a-hole-while-its-punched.patch and replace it by 1/2, which fixes that commit instead of reverting it. Please throw away mmotm's shmem-fix-faulting-into-a-hole-while-its-punched-take-2.patch and replace it by 2/2, which reworks the commit message and adds a fix. Please keep the 3/3 I sent last time in mmotm mm-fs-fix-pessimization-in-hole-punching-pagecache.patch which remains valid. In the end I decided that we had better look at it as two problems, the trinity faulting starvation, and the indefinite punching loop, so 1/2 and 2/2 present both solutions: belt and braces. Which may be the best for fixing, but the worst for ease of backporting. Vlastimil, I have prepared (and lightly tested) a 3.2.61-based version of the combination of f00cdc6df7d7 and 1/2 and 2/2 (basically, I moved vmtruncate_range from mm/truncate.c to mm/shmem.c, since nothing but shmem ever implemented the truncate_range method). It should give a good hint for backports earlier and later: I'll send it privately to you now, but keep in mind that it may need to be revised if today's patches for 3.16 get revised again (I'll send it to Ben Hutchings only when that's settled). Thanks, Hugh -- 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
