From: bfields@fieldses.org (J. Bruce Fields)
To: Chuck Lever III <chuck.lever@oracle.com>
Cc: Neil Brown <neilb@suse.de>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [RFC PATCH 0/4] nfsd: allow NFSv4 state to be revoked.
Date: Fri, 28 Jan 2022 10:03:34 -0500 [thread overview]
Message-ID: <20220128150334.GD14908@fieldses.org> (raw)
In-Reply-To: <C462D2BB-BD5B-4372-B644-FD4D6D877072@oracle.com>
On Fri, Jan 28, 2022 at 01:46:45PM +0000, Chuck Lever III wrote:
> My initial impulse is to better understand what is preventing
> the unexported filesystem from being unmounted. Better
> observability there could potentially be of value.
In theory that information's in /proc/fs/nfsd/clients/. Somebody could
write a tool to scan that for state referencing a given filesystem.
--b.
next prev parent reply other threads:[~2022-01-28 15:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 4:58 [RFC PATCH 0/4] nfsd: allow NFSv4 state to be revoked NeilBrown
2022-01-27 4:58 ` [PATCH 1/4] nfsd: prepare for supporting admin-revocation of state NeilBrown
2022-01-27 12:59 ` kernel test robot
2022-01-27 14:51 ` kernel test robot
2022-01-27 4:58 ` [PATCH 4/4] nfsd: allow delegation state ids to be revoked and then freed NeilBrown
2022-01-27 4:58 ` [PATCH 3/4] nfsd: allow lock " NeilBrown
2022-01-27 4:58 ` [PATCH 2/4] nfsd: allow open " NeilBrown
2022-01-27 17:00 ` [RFC PATCH 0/4] nfsd: allow NFSv4 state to be revoked Chuck Lever III
2022-01-27 22:41 ` NeilBrown
2022-01-27 23:15 ` dai.ngo
2022-01-28 0:07 ` Chuck Lever III
2022-01-28 4:24 ` NeilBrown
2022-01-28 4:35 ` Trond Myklebust
2022-01-28 13:46 ` Chuck Lever III
2022-01-28 15:03 ` J. Bruce Fields [this message]
2022-01-28 2:51 ` J. Bruce Fields
2022-01-28 4:14 ` NeilBrown
2022-01-28 13:38 ` J. Bruce Fields
2022-01-28 16:23 ` J. Bruce Fields
2022-01-27 20:06 ` J. Bruce Fields
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=20220128150334.GD14908@fieldses.org \
--to=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
/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