linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Al Viro <viro@zeniv.linux.org.uk>
To: Richard Weinberger <richard@nod.at>
Cc: chuck lever <chuck.lever@oracle.com>,
	linux-nfs <linux-nfs@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	Jeff Layton <jlayton@kernel.org>, anna <anna@kernel.org>,
	trond myklebust <trond.myklebust@hammerspace.com>,
	raven <raven@themaw.net>,
	chris chilvers <chris.chilvers@appsbroker.com>,
	david young <david.young@appsbroker.com>,
	luis turcitu <luis.turcitu@appsbroker.com>,
	david <david@sigma-star.at>, benmaynard <benmaynard@google.com>
Subject: Re: [PATCH 2/3] namei: Allow follow_down() to uncover auto mounts
Date: Mon, 30 Jan 2023 02:15:52 +0000	[thread overview]
Message-ID: <Y9coWGadefHY6ZEJ@ZenIV> (raw)
In-Reply-To: <68008696.79813.1675006959005.JavaMail.zimbra@nod.at>

On Sun, Jan 29, 2023 at 04:42:39PM +0100, Richard Weinberger wrote:
> ----- Ursprüngliche Mail -----
> > Von: "chuck lever" <chuck.lever@oracle.com>
> >> On Dec 7, 2022, at 3:43 AM, Richard Weinberger <richard@nod.at> wrote:
> >> 
> >> This function is only used by NFSD to cross mount points.
> >> If a mount point is of type auto mount, follow_down() will
> >> not uncover it. Add LOOKUP_AUTOMOUNT to the lookup flags
> >> to have ->d_automount() called when NFSD walks down the
> >> mount tree.
> >> 
> >> Signed-off-by: Richard Weinberger <richard@nod.at>
> > 
> > Hello Al, you are top of the maintainers listed for fs/namei.c.
> > I'd like to take this series for v6.3 via the nfsd tree. Can
> > I get your Acked-by: for this one?
> 
> ping?

modulo clumsy wording ("mount point is of type auto mount")

Acked-by: Al Viro <viro@zeniv.linux.org.uk>

Commit message sounds as if it refered to autofs, rather than NFS referrals
et.al. and AFAICS those are the cases it's really about...

  reply	other threads:[~2023-01-30  2:16 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-07  8:43 [PATCH 0/3 v2] NFS: NFSD: Allow crossing mounts when re-exporting Richard Weinberger
2022-12-07  8:43 ` [PATCH 1/3] NFSD: Teach nfsd_mountpoint() auto mounts Richard Weinberger
2022-12-07  8:43 ` [PATCH 2/3] fs: namei: Allow follow_down() to uncover " Richard Weinberger
2022-12-14 15:15   ` [PATCH 2/3] " Chuck Lever III
2023-01-03 16:15   ` Chuck Lever III
2023-01-29 15:42     ` Richard Weinberger
2023-01-30  2:15       ` Al Viro [this message]
2022-12-07  8:43 ` [PATCH 3/3] NFS: nfs_encode_fh: Remove S_AUTOMOUNT check Richard Weinberger
2022-12-14 15:09   ` Chuck Lever III
2022-12-14 16:37     ` Anna Schumaker
2022-12-14 16:39       ` Chuck Lever III
2022-12-10 16:09 ` [PATCH 0/3 v2] NFS: NFSD: Allow crossing mounts when re-exporting Chuck Lever III
2022-12-10 21:52   ` Richard Weinberger
2022-12-10 21:53     ` Chuck Lever III
2022-12-12 17:06 ` Jeff Layton
2022-12-13  9:09   ` 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=Y9coWGadefHY6ZEJ@ZenIV \
    --to=viro@zeniv.linux.org.uk \
    --cc=anna@kernel.org \
    --cc=benmaynard@google.com \
    --cc=chris.chilvers@appsbroker.com \
    --cc=chuck.lever@oracle.com \
    --cc=david.young@appsbroker.com \
    --cc=david@sigma-star.at \
    --cc=jlayton@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=luis.turcitu@appsbroker.com \
    --cc=raven@themaw.net \
    --cc=richard@nod.at \
    --cc=trond.myklebust@hammerspace.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).