All of lore.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@zeniv.linux.org.uk>
To: Ian Kent <raven@themaw.net>
Cc: Christian Brauner <brauner@kernel.org>,
	autofs mailing list <autofs@vger.kernel.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] autofs: add per dentry expire timeout
Date: Wed, 14 Aug 2024 06:45:52 +0100	[thread overview]
Message-ID: <20240814054552.GR13701@ZenIV> (raw)
In-Reply-To: <20240814035037.44267-1-raven@themaw.net>

On Wed, Aug 14, 2024 at 11:50:37AM +0800, Ian Kent wrote:

> +		inode_lock_shared(inode);
> +		dentry = try_lookup_one_len(param->path, base, path_len);
> +		inode_unlock_shared(inode);
> +		if (!dentry)
> +			return -ENOENT;
> +		ino = autofs_dentry_ino(dentry);

Why can't we get ERR_PTR(...) from try_lookup_one_len() here?

  reply	other threads:[~2024-08-14  5:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-14  3:50 [PATCH] autofs: add per dentry expire timeout Ian Kent
2024-08-14  5:45 ` Al Viro [this message]
2024-08-14  8:00   ` Ian Kent

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=20240814054552.GR13701@ZenIV \
    --to=viro@zeniv.linux.org.uk \
    --cc=autofs@vger.kernel.org \
    --cc=brauner@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=raven@themaw.net \
    /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.