From: Gu Zheng <guzheng1@huawei.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: <jlayton@poochiereds.net>, <linux-nfs@vger.kernel.org>,
<houtao1@huawei.com>, Zhaohongjiang <zhaohongjiang@huawei.com>,
<miaoxie@huawei.com>, Kinglong Mee <kinglongmee@gmail.com>
Subject: Re: nfs+ext4,can not umount the ext4 mountpoint
Date: Thu, 18 May 2017 18:59:33 +0800 [thread overview]
Message-ID: <591D7E95.5030109@huawei.com> (raw)
In-Reply-To: <20170517154648.GB30168@fieldses.org>
to J. Bruce Fields:
thanks for your supports.
to Kinglong Mee:
I warried about how to modify for supporting the expected unmount.
It is helpful to me after i saw the patchs,but it felt a little unreasonably in bellow scene:
if a filesystem is exported and i am in the mounted directory on client,the fs also can be umounted on server.
best wishes!
在 2017/5/17 23:46, J. Bruce Fields 写道:
> On Wed, May 17, 2017 at 03:18:38PM +0800, Gu Zheng wrote:
>> and now we do not set the crossmnt ,so that we saw is the underlying directory .
>> the nfs mount have no relation to ext4 mountpoint, it can be umounted maybe better.
>>
>> can we add some limits to let it do not enter the nfsd_cross_mnt() in nfsd_lookup_dentry()if the crossmnt is not set?
>
> If the problem is inability to unmount a filesystem that isn't actually
> even exported, then it *might* be addressed by Kinglong Mee's patches:
>
> http://lkml.kernel.org/r/55ED9899.9010401@gmail.com
>
> I'm not sure what those patches still need--they may just be waiting for
> my review.
>
> --b
>
> .
>
prev parent reply other threads:[~2017-05-18 11:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-16 12:57 nfs+ext4,can not umount the ext4 mountpoint Gu Zheng
2017-05-16 17:42 ` J. Bruce Fields
2017-05-17 7:18 ` Gu Zheng
2017-05-17 15:46 ` J. Bruce Fields
2017-05-18 10:59 ` Gu Zheng [this message]
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=591D7E95.5030109@huawei.com \
--to=guzheng1@huawei.com \
--cc=bfields@fieldses.org \
--cc=houtao1@huawei.com \
--cc=jlayton@poochiereds.net \
--cc=kinglongmee@gmail.com \
--cc=linux-nfs@vger.kernel.org \
--cc=miaoxie@huawei.com \
--cc=zhaohongjiang@huawei.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 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.