From: "Theodore Ts'o" <tytso@mit.edu>
To: Eric Biggers <ebiggers@kernel.org>
Cc: linux-unionfs@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-fscrypt@vger.kernel.org, linux-mtd@lists.infradead.org,
Sarthak Kukreti <sarthakkukreti@chromium.org>,
linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: [PATCH v2 1/5] fscrypt: clean up and improve dentry revalidation
Date: Wed, 17 Apr 2019 09:50:15 -0400 [thread overview]
Message-ID: <20190417135015.GA4686@mit.edu> (raw)
In-Reply-To: <20190417001041.GA18090@gmail.com>
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
WARNING: multiple messages have this Message-ID (diff)
From: "Theodore Ts'o" <tytso@mit.edu>
To: Eric Biggers <ebiggers@kernel.org>
Cc: linux-fscrypt@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-mtd@lists.infradead.org, linux-unionfs@vger.kernel.org,
Sarthak Kukreti <sarthakkukreti@chromium.org>,
Gao Xiang <gaoxiang25@huawei.com>
Subject: Re: [PATCH v2 1/5] fscrypt: clean up and improve dentry revalidation
Date: Wed, 17 Apr 2019 09:50:15 -0400 [thread overview]
Message-ID: <20190417135015.GA4686@mit.edu> (raw)
In-Reply-To: <20190417001041.GA18090@gmail.com>
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
WARNING: multiple messages have this Message-ID (diff)
From: "Theodore Ts'o" <tytso@mit.edu>
To: Eric Biggers <ebiggers@kernel.org>
Cc: Gao Xiang <gaoxiang25@huawei.com>,
linux-unionfs@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-fscrypt@vger.kernel.org, linux-mtd@lists.infradead.org,
Sarthak Kukreti <sarthakkukreti@chromium.org>,
linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: [PATCH v2 1/5] fscrypt: clean up and improve dentry revalidation
Date: Wed, 17 Apr 2019 09:50:15 -0400 [thread overview]
Message-ID: <20190417135015.GA4686@mit.edu> (raw)
In-Reply-To: <20190417001041.GA18090@gmail.com>
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
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2019-04-17 13:50 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-20 18:39 [PATCH v2 0/5] fscrypt: d_revalidate fixes and cleanups Eric Biggers
2019-03-20 18:39 ` Eric Biggers
2019-03-20 18:39 ` Eric Biggers
2019-03-20 18:39 ` [PATCH v2 1/5] fscrypt: clean up and improve dentry revalidation Eric Biggers
2019-03-20 18:39 ` Eric Biggers
2019-03-20 18:39 ` Eric Biggers
2019-03-20 18:39 ` [f2fs-dev] " Eric Biggers
2019-04-16 23:08 ` Theodore Ts'o
2019-04-16 23:08 ` Theodore Ts'o
2019-04-17 0:10 ` Eric Biggers
2019-04-17 0:10 ` Eric Biggers
2019-04-17 0:10 ` Eric Biggers
2019-04-17 0:10 ` [f2fs-dev] " Eric Biggers
2019-04-17 13:50 ` Theodore Ts'o [this message]
2019-04-17 13:50 ` Theodore Ts'o
2019-04-17 13:50 ` Theodore Ts'o
2019-03-20 18:39 ` [PATCH v2 2/5] fscrypt: fix race allowing rename() and link() of ciphertext dentries Eric Biggers
2019-03-20 18:39 ` Eric Biggers
2019-03-20 18:39 ` Eric Biggers
2019-03-20 18:39 ` [f2fs-dev] " Eric Biggers
2019-04-17 13:53 ` Theodore Ts'o
2019-04-17 13:53 ` Theodore Ts'o
2019-04-17 13:53 ` Theodore Ts'o
2019-03-20 18:39 ` [PATCH v2 3/5] fs, fscrypt: clear DCACHE_ENCRYPTED_NAME when unaliasing directory Eric Biggers
2019-03-20 18:39 ` Eric Biggers
2019-03-20 18:39 ` Eric Biggers
2019-04-17 14:06 ` Theodore Ts'o
2019-04-17 14:06 ` Theodore Ts'o
2019-03-20 18:39 ` [PATCH v2 4/5] fscrypt: only set dentry_operations on ciphertext dentries Eric Biggers
2019-03-20 18:39 ` Eric Biggers
2019-03-20 18:39 ` Eric Biggers
2019-03-20 18:39 ` [f2fs-dev] " Eric Biggers
2019-04-17 14:07 ` Theodore Ts'o
2019-04-17 14:07 ` Theodore Ts'o
2019-04-17 14:07 ` Theodore Ts'o
2019-03-20 18:39 ` [PATCH v2 5/5] fscrypt: fix race where ->lookup() marks plaintext dentry as ciphertext Eric Biggers
2019-03-20 18:39 ` Eric Biggers
2019-03-20 18:39 ` Eric Biggers
2019-03-20 18:39 ` [f2fs-dev] " Eric Biggers
2019-04-17 14:24 ` Theodore Ts'o
2019-04-17 14:24 ` Theodore Ts'o
2019-04-17 14:24 ` Theodore Ts'o
2019-04-01 17:11 ` [PATCH v2 0/5] fscrypt: d_revalidate fixes and cleanups Eric Biggers
2019-04-01 17:11 ` Eric Biggers
2019-04-01 17:11 ` Eric Biggers
2019-04-01 17:11 ` [f2fs-dev] " Eric Biggers
2019-04-08 8:22 ` Richard Weinberger
2019-04-08 8:22 ` Richard Weinberger
2019-04-08 8:22 ` Richard Weinberger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190417135015.GA4686@mit.edu \
--to=tytso@mit.edu \
--cc=ebiggers@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=sarthakkukreti@chromium.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.