On Tue, Jan 24, 2017 at 03:37:00PM -0800, Eric Biggers wrote: > From: Eric Biggers <ebiggers@xxxxxxxxxx> > > In the case where the child's encryption context was inconsistent with > its parent directory, we were using inode->i_sb and inode->i_ino after > the inode had already been iput(). Fix this by doing the iput() in the > correct places. > > Note: only ext4 had this bug, not f2fs and ubifs. > > Fixes: d9cdc9033181 ("ext4 crypto: enforce context consistency") > Cc: stable@xxxxxxxxxxxxxxx > Signed-off-by: Eric Biggers <ebiggers@xxxxxxxxxx> Thanks, applied. - 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
![]() |