From: "J. Bruce Fields" <bfields@fieldses.org>
To: Kinglong Mee <kinglongmee@gmail.com>
Cc: Steve Dickson <SteveD@redhat.com>,
linux-nfs@vger.kernel.org, Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH] exportfs: Make sure pass all valid export flags to nfsd
Date: Wed, 11 Jan 2017 09:16:50 -0500 [thread overview]
Message-ID: <20170111141650.GA18977@fieldses.org> (raw)
In-Reply-To: <49b7be0a-548a-cff1-8f09-613cd5c63141@gmail.com>
On Sat, Jan 07, 2017 at 07:57:28PM +0800, Kinglong Mee wrote:
> On 1/7/2017 05:05, J. Bruce Fields wrote:
> > On Sat, Dec 31, 2016 at 09:05:11PM +0800, Kinglong Mee wrote:
> >> test_export pass a export flags only marks NFSEXP_FSID,
> >> nfsd may want other flags for export checking.
> >
> > Why? What problem does this fix?
>
> When testing the patch "NFSD: Only support readonly export for
> !fsync and readonly filesystem", I found exportfs don't pass
> all valid export flags to nfsd. So, make this patch.
This function is meant to test whether a filesystem supports nfs export
or not. It doesn't need the full set of export flags. Off the top of
my head I can't see reason this would cause problems, but I'm not
convinced it's safe, either. (New nfs-utils against old kernels might
be a case to check, e.g. to see how unsupported flags are handled.)
So until we have a reason we *need* this, just to be safe, I'd prefer to
revert this patch.
--b.
>
> thanks,
> Kinglong Mee
>
> >
> > --b.
> >
> >> This patch make sure exportfs pass all other flags to nfsd.
> >>
> >> Signed-off-by: Kinglong Mee <kinglongmee@gmail.com>
> >> ---
> >> utils/exportfs/exportfs.c | 12 +++++++-----
> >> 1 file changed, 7 insertions(+), 5 deletions(-)
> >>
> >> diff --git a/utils/exportfs/exportfs.c b/utils/exportfs/exportfs.c
> >> index 15a1583..bacf106 100644
> >> --- a/utils/exportfs/exportfs.c
> >> +++ b/utils/exportfs/exportfs.c
> >> @@ -473,8 +473,10 @@ static int can_test(void)
> >> return 1;
> >> }
> >>
> >> -static int test_export(char *path, int with_fsid)
> >> +static int test_export(nfs_export *exp, int with_fsid)
> >> {
> >> + char *path = exp->m_export.e_path;
> >> + int flags = exp->m_export.e_flags | (with_fsid ? NFSEXP_FSID : 0);
> >> /* beside max path, buf size should take protocol str into account */
> >> char buf[NFS_MAXPATHLEN+1+64] = { 0 };
> >> char *bp = buf;
> >> @@ -487,7 +489,7 @@ static int test_export(char *path, int with_fsid)
> >> qword_add(&bp, &len, path);
> >> if (len < 1)
> >> return 0;
> >> - snprintf(bp, len, " 3 %d 65534 65534 0\n", with_fsid ? NFSEXP_FSID : 0);
> >> + snprintf(bp, len, " 3 %d 65534 65534 0\n", flags);
> >> fd = open("/proc/net/rpc/nfsd.export/channel", O_WRONLY);
> >> if (fd < 0)
> >> return 0;
> >> @@ -529,12 +531,12 @@ validate_export(nfs_export *exp)
> >>
> >> if ((exp->m_export.e_flags & NFSEXP_FSID) || exp->m_export.e_uuid ||
> >> fs_has_fsid) {
> >> - if ( !test_export(path, 1)) {
> >> + if ( !test_export(exp, 1)) {
> >> xlog(L_ERROR, "%s does not support NFS export", path);
> >> return;
> >> }
> >> - } else if ( ! test_export(path, 0)) {
> >> - if (test_export(path, 1))
> >> + } else if ( !test_export(exp, 0)) {
> >> + if (test_export(exp, 1))
> >> xlog(L_ERROR, "%s requires fsid= for NFS export", path);
> >> else
> >> xlog(L_ERROR, "%s does not support NFS export", path);
> >> --
> >> 2.9.3
> >>
> >> --
> >> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> >> the body of a message to majordomo@vger.kernel.org
> >> More majordomo info at http://vger.kernel.org/majordomo-info.html
> >
next prev parent reply other threads:[~2017-01-11 14:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-31 13:05 [PATCH] exportfs: Make sure pass all valid export flags to nfsd Kinglong Mee
2017-01-04 16:56 ` Steve Dickson
2017-01-06 21:05 ` J. Bruce Fields
2017-01-07 11:57 ` Kinglong Mee
2017-01-11 14:16 ` J. Bruce Fields [this message]
2017-01-15 7:43 ` Kinglong Mee
2017-01-16 16:54 ` J. Bruce Fields
2017-01-18 10:16 ` Kinglong Mee
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=20170111141650.GA18977@fieldses.org \
--to=bfields@fieldses.org \
--cc=SteveD@redhat.com \
--cc=hch@infradead.org \
--cc=kinglongmee@gmail.com \
--cc=linux-nfs@vger.kernel.org \
/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.