[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Wed, 1 Feb 2017 21:17:36 -0500
From: Theodore Ts'o <tytso@....edu>
To: Eric Biggers <ebiggers3@...il.com>
Cc: linux-ext4@...r.kernel.org, linux-fscrypt@...r.kernel.org,
Andreas Dilger <adilger.kernel@...ger.ca>,
Eric Biggers <ebiggers@...gle.com>, stable@...r.kernel.org
Subject: Re: [PATCH] ext4: fix use-after-iput when fscrypt contexts are
inconsistent
On Tue, Jan 24, 2017 at 03:37:00PM -0800, Eric Biggers wrote:
> From: Eric Biggers <ebiggers@...gle.com>
>
> 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@...r.kernel.org
> Signed-off-by: Eric Biggers <ebiggers@...gle.com>
Thanks, applied.
- Ted
Powered by blists - more mailing lists