From: Kinglong Mee <kinglongmee@gmail.com>
To: houlinfei <hou.linfei@h3c.com>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
bfields@fieldses.org, neilb@suse.com, SteveD@redhat.com,
Kinglong Mee <kinglongmee@gmail.com>
Subject: Re: some problems about permission of subdirectory
Date: Wed, 22 Feb 2017 16:00:36 +0800 [thread overview]
Message-ID: <39acaddb-d4c0-dbda-3e22-11b865d4b9ec@gmail.com> (raw)
In-Reply-To: <24b92a5f.6561.15a64adfe18.Coremail.hou.linfei@h3c.com>
On 2/22/2017 15:16, houlinfei wrote:
> hi Kinglong:
> Thank you for your answer about this phenomenon, i just try the method you provide, but problem also exist. If i want to change the code about nfsd and rpc.mountd, where should i change? I'm not familiar with this part of the code.
Sorry, I test it with the following sets (with "no_root_squash"),
/root/hh/hh1 *(rw,no_subtree_check,no_root_squash,insecure)
It's okay for your problem, but all client's process will be treated as root.
But, it's just a hacker method with many limits,
I think you'd better change your exports as,
/root/hh/hh1 *(ro,sync,insecure,no_subtree_check)
/root/hh/hh2 *(rw,sync,insecure,no_subtree_check)
thanks,
Kinglong Mee
next prev parent reply other threads:[~2017-02-22 8:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-22 7:16 some problems about permission of subdirectory houlinfei
2017-02-22 8:00 ` Kinglong Mee [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-02-25 13:26 houlinfei
2017-02-26 0:23 ` Kinglong Mee
2017-02-25 9:44 houlinfei
2017-02-25 10:51 ` Kinglong Mee
2017-02-23 15:21 houlinfei
2017-02-23 3:53 houlinfei
2017-02-23 8:18 ` Kinglong Mee
2017-02-21 8:52 houlinfei
2017-02-21 13:50 ` Kinglong Mee
2017-02-24 19:14 ` J. Bruce Fields
2017-02-25 10:45 ` 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=39acaddb-d4c0-dbda-3e22-11b865d4b9ec@gmail.com \
--to=kinglongmee@gmail.com \
--cc=SteveD@redhat.com \
--cc=bfields@fieldses.org \
--cc=hou.linfei@h3c.com \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.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).