[lustre-devel] Do we need LOOKUP_CONTINUE in ll_revalidate_dentry()
NeilBrown
neilb at suse.com
Sun Nov 25 23:25:50 PST 2018
On Mon, Nov 26 2018, James Simmons wrote:
> Doing a compare to the OpenSFS branch I noticed this difference:
>
> diff --git a/drivers/staging/lustre/lustre/llite/dcache.c
> b/drivers/staging/lustre/lustre/llite/dcache.c
> index 11b82c63..6ee0ec9 100644
> --- a/drivers/staging/lustre/lustre/llite/dcache.c
> +++ b/drivers/staging/lustre/lustre/llite/dcache.c
> @@ -254,7 +254,7 @@ static int ll_revalidate_dentry(struct dentry *dentry,
> * to this dentry, then its lock has not been revoked and the
> * path component is valid.
> */
> - if (lookup_flags & LOOKUP_PARENT)
> + if (lookup_flags & (LOOKUP_CONTINUE | LOOKUP_PARENT))
> return 1;
>
> /* Symlink - always valid as long as the dentry was found */
>
> Is that needed for newer kernels?
LOOKUP_CONTINUE disappeared in 2011
Commit: 49084c3bb205 ("kill LOOKUP_CONTINUE")
LOOKUP_PARENT is the new LOOKUP_CONTINUE.
NeilBrown
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: not available
URL: <http://lists.lustre.org/pipermail/lustre-devel-lustre.org/attachments/20181126/1d212677/attachment.sig>
More information about the lustre-devel
mailing list