[PATCH v2 2/3] fscrypt: Have filesystems handle their d_ops
Jaegeuk Kim
jaegeuk at kernel.org
Tue Nov 17 12:04:11 EST 2020
On 11/17, Theodore Y. Ts'o wrote:
> On Tue, Nov 17, 2020 at 04:03:14AM +0000, Daniel Rosenberg wrote:
> > This shifts the responsibility of setting up dentry operations from
> > fscrypt to the individual filesystems, allowing them to have their own
> > operations while still setting fscrypt's d_revalidate as appropriate.
> >
> > Most filesystems can just use generic_set_encrypted_ci_d_ops, unless
> > they have their own specific dentry operations as well. That operation
> > will set the minimal d_ops required under the circumstances.
> >
> > Since the fscrypt d_ops are set later on, we must set all d_ops there,
> > since we cannot adjust those later on. This should not result in any
> > change in behavior.
> >
> > Signed-off-by: Daniel Rosenberg <drosen at google.com>
>
> Acked-by: Theodore Ts'o <tytso at mit.edu>
Hi Ted/Richard,
I'd like to pick this patch series in f2fs/dev for -next, so please let me know
if you have any concern.
Thanks,
More information about the linux-mtd
mailing list