On Tue, May 02, 2017 at 10:36:01AM -0700, Eric Biggers wrote: > Ted, can you add Cc stable to this commit? (Just this one; the others in the > series aren't as important.) I think this fix is more important than I > originally thought, because it's actually pretty easy to end up in a situation > where a directory has its key but a file in it does not, due to the file's inode > having been evicted from the inode cache but not the directory's inode. This > makes the file undeletable. Done. This meant I had to do a rewind on the fscrypt tree, so if someone has built something on top of fscrypt since Sunday you may need to take special precautions. This was just a change to the commit description so git rebase should take of the problem relatively easily. - Ted -- To unsubscribe from this list: send the line "unsubscribe linux-fscrypt" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
|