[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190417135015.GA4686@mit.edu>
Date: Wed, 17 Apr 2019 09:50:15 -0400
From: "Theodore Ts'o" <tytso@....edu>
To: Eric Biggers <ebiggers@...nel.org>
Cc: linux-fscrypt@...r.kernel.org, linux-fsdevel@...r.kernel.org,
linux-ext4@...r.kernel.org, linux-f2fs-devel@...ts.sourceforge.net,
linux-mtd@...ts.infradead.org, linux-unionfs@...r.kernel.org,
Sarthak Kukreti <sarthakkukreti@...omium.org>,
Gao Xiang <gaoxiang25@...wei.com>
Subject: Re: [PATCH v2 1/5] fscrypt: clean up and improve dentry revalidation
On Tue, Apr 16, 2019 at 05:10:42PM -0700, Eric Biggers wrote:
>
> Hi Ted, I assumed you resolved the conflict with "fscrypt: use READ_ONCE() to
> access ->i_crypt_info"? The code in fscrypt_d_revalidate() should be:
>
> dir = dget_parent(dentry);
> err = fscrypt_get_encryption_info(d_inode(dir));
> valid = !fscrypt_has_encryption_key(d_inode(dir));
> dput(dir);
Yes, I did notice the patch conflict. Thanks for confirming the
correct resolution!
- Ted
Powered by blists - more mailing lists