From: Amir Goldstein <amir73il@gmail.com>
To: Christian Brauner <brauner@kernel.org>
Cc: Chuck Lever <chuck.lever@oracle.com>,
Jeff Layton <jlayton@kernel.org>, Christoph Hellwig <hch@lst.de>,
Neil Brown <neil@brown.name>, Jan Kara <jack@suse.cz>,
linux-fsdevel@vger.kernel.org, linux-nfs@vger.kernel.org
Subject: [PATCH v4 0/2] nfsd and special kernel filesystems
Date: Thu, 29 Jan 2026 11:02:10 +0100 [thread overview]
Message-ID: <20260129100212.49727-1-amir73il@gmail.com> (raw)
Christian,
This v4 addresses Chuck and Jeff's review on v3.
The first doc patch is applicable to the doc update in vfs-7.0.misc.
The 2nd fix patch is independent of the doc changes in vfs-7.0.misc,
so it should be easier to backport.
Thanks,
Amir.
Changes since v3:
- Fix typo and doc comments from Chunk
- Add RVB
Changes since v2:
- Rebase over vfs-7.0.misc
- Split to doc/fix patches
- Remove RVBs
Amir Goldstein (2):
exportfs: clarify the documentation of open()/permission() expotrfs
ops
nfsd: do not allow exporting of special kernel filesystems
fs/nfsd/export.c | 8 +++++---
include/linux/exportfs.h | 21 +++++++++++++++++++--
2 files changed, 24 insertions(+), 5 deletions(-)
--
2.52.0
next reply other threads:[~2026-01-29 10:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-29 10:02 Amir Goldstein [this message]
2026-01-29 10:02 ` [PATCH v4 1/2] exportfs: clarify the documentation of open()/permission() expotrfs ops Amir Goldstein
2026-01-29 10:02 ` [PATCH v4 2/2] nfsd: do not allow exporting of special kernel filesystems Amir Goldstein
2026-01-29 14:00 ` [PATCH v4 0/2] nfsd and " Chuck Lever
2026-01-29 16:27 ` Christian Brauner
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=20260129100212.49727-1-amir73il@gmail.com \
--to=amir73il@gmail.com \
--cc=brauner@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=jlayton@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neil@brown.name \
/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