From: Chuck Lever III <chuck.lever@oracle.com>
To: Richard Weinberger <richard@nod.at>
Cc: Linux NFS Mailing List <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>,
Al Viro <viro@zeniv.linux.org.uk>, 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@google.com" <benmaynard@google.com>
Subject: Re: [PATCH 0/3 v2] NFS: NFSD: Allow crossing mounts when re-exporting
Date: Sat, 10 Dec 2022 21:53:54 +0000 [thread overview]
Message-ID: <92ED1723-4F11-4F48-9B4D-089F29AE91A7@oracle.com> (raw)
In-Reply-To: <1733592831.372285.1670709120777.JavaMail.zimbra@nod.at>
> On Dec 10, 2022, at 4:52 PM, Richard Weinberger <richard@nod.at> wrote:
>
> ----- Ursprüngliche Mail -----
>> Von: "chuck lever" <chuck.lever@oracle.com>
>>> Richard Weinberger (3):
>>> NFSD: Teach nfsd_mountpoint() auto mounts
>>> fs: namei: Allow follow_down() to uncover auto mounts
>>> NFS: nfs_encode_fh: Remove S_AUTOMOUNT check
>>>
>>> fs/namei.c | 6 +++---
>>> fs/nfs/export.c | 2 +-
>>> fs/nfsd/vfs.c | 8 ++++++--
>>> include/linux/namei.h | 2 +-
>>> 4 files changed, 11 insertions(+), 7 deletions(-)
>>>
>>> --
>>> 2.26.2
>>>
>>
>> This series is a bit late for inclusion in v6.2. The next opportunity
>> will be v6.3 in a couple of months. I prefer to have a "final" version
>> of patches by -rc5.
>>
>> I'm waiting for review comments on v2 of this series.
>
> Ok! Do you want me to resend the series in any case by v6.2-rc5 or only
> if new comments arise?
If v2 garners no new comments, then send a reminder with a URL to this
thread on lore.kernel.org. I will pull the series from there.
--
Chuck Lever
next prev parent reply other threads:[~2022-12-10 21:54 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
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 [this message]
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=92ED1723-4F11-4F48-9B4D-089F29AE91A7@oracle.com \
--to=chuck.lever@oracle.com \
--cc=anna@kernel.org \
--cc=benmaynard@google.com \
--cc=chris.chilvers@appsbroker.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 \
--cc=viro@zeniv.linux.org.uk \
/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).