archive mirror
 help / color / mirror / Atom feed
From: "Aurélien Aptel" <>
Cc:, Aurelien Aptel <>
Subject: [PATCH] Documentation/admin-guide/cifs: document open_files and dfscache
Date: Mon, 22 Mar 2021 18:34:37 +0100	[thread overview]
Message-ID: <> (raw)

From: Aurelien Aptel <>

Add missing documentation for open_files and dfscache /proc files.

Signed-off-by: Aurelien Aptel <>
 Documentation/admin-guide/cifs/usage.rst | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/Documentation/admin-guide/cifs/usage.rst b/Documentation/admin-guide/cifs/usage.rst
index 13783dc68ab7..f170d8820258 100644
--- a/Documentation/admin-guide/cifs/usage.rst
+++ b/Documentation/admin-guide/cifs/usage.rst
@@ -714,6 +714,7 @@ DebugData		Displays information about active CIFS sessions and
 Stats			Lists summary resource usage information as well as per
 			share statistics.
+open_files		List all the open file handles on all active SMB sessions.
 ======================= =======================================================
 Configuration pseudo-files:
@@ -794,6 +795,8 @@ LinuxExtensionsEnabled	If set to one then the client will attempt to
 			support and want to map the uid and gid fields
 			to values supplied at mount (rather than the
 			actual values, then set this to zero. (default 1)
+dfscache		List the content of the DFS cache.
+			If set to 0, the client will clear the cache.
 ======================= =======================================================
 These experimental features and tracing can be enabled by changing flags in

             reply	other threads:[~2021-03-22 17:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-22 17:34 Aurélien Aptel [this message]
2021-03-22 19:31 ` [PATCH] Documentation/admin-guide/cifs: document open_files and dfscache Paulo Alcantara
2021-04-09  4:31   ` Steve French

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).