archive mirror
 help / color / mirror / Atom feed
From: Ian Kent <>
To: Andrew Morton <>
Cc: Kernel Mailing List <>,
	autofs mailing list <>,
	linux-fsdevel <>
Subject: [PATCH 4/5] autofs - update mount control expire desription with AUTOFS_EXP_FORCED
Date: Mon, 18 Mar 2019 09:00:40 +0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Describe AUTOFS_EXP_FORCED in addition to AUTOFS_EXP_IMMEDIATE in the
description of the AUTOFS_DEV_IOCTL_EXPIRE_CMD ioctl.

Signed-off-by: Ian Kent <>
 Documentation/filesystems/autofs-mount-control.txt |    6 ++++--
 Documentation/filesystems/autofs.txt               |    5 +++++
 2 files changed, 9 insertions(+), 2 deletions(-)

diff --git a/Documentation/filesystems/autofs-mount-control.txt b/Documentation/filesystems/autofs-mount-control.txt
index 45edad6933cc..acc02fc57993 100644
--- a/Documentation/filesystems/autofs-mount-control.txt
+++ b/Documentation/filesystems/autofs-mount-control.txt
@@ -354,8 +354,10 @@ this ioctl is called until no further expire candidates are found.
 The call requires an initialized struct autofs_dev_ioctl with the
 ioctlfd field set to the descriptor obtained from the open call. In
-addition an immediate expire, independent of the mount timeout, can be
-requested by setting the how field of struct args_expire to 1. If no
+addition an immediate expire that's independent of the mount timeout,
+and a forced expire that's independent of whether the mount is busy,
+can be requested by setting the how field of struct args_expire to
 expire candidates can be found the ioctl returns -1 with errno set to
diff --git a/Documentation/filesystems/autofs.txt b/Documentation/filesystems/autofs.txt
index 8fe43c97cb96..409e6411904d 100644
--- a/Documentation/filesystems/autofs.txt
+++ b/Documentation/filesystems/autofs.txt
@@ -410,6 +410,11 @@ The available ioctl commands are:
      **AUTOFS_EXP_IMMEDIATE** causes `last_used` time to be ignored
      and objects are expired if the are not in use.
+     **AUTOFS_EXP_FORCED** causes the in use status to be ignored
+     and objects are expired ieven if they are in use. This assumes
+     that the daemon has requested this because it is capable of
+     performing the umount.
      **AUTOFS_EXP_LEAVES** will select a leaf rather than a top-level
      name to expire.  This is only safe when *maxproto* is 4.

  parent reply	other threads:[~2019-03-18  1:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-18  1:00 [PATCH 1/5] autofs - fix some word usage odities in autofs.txt Ian Kent
2019-03-18  1:00 ` [PATCH 2/5] autofs - update autofs.txt for strictexpire mount option Ian Kent
2019-03-18  1:00 ` [PATCH 3/5] autofs - update AUTOFS_EXP_LEAVES description Ian Kent
2019-03-18  1:00 ` Ian Kent [this message]
2019-03-18  1:00 ` [PATCH 5/5] autofs - add description of ignore pseudo mount option Ian Kent

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