From: NeilBrown <neilb@suse.com>
Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: [PATCH manpages] umount.2: restore mention of data loss with MNT_FORCE
Date: Thu, 10 Aug 2017 13:23:38 +1000 [thread overview]
Message-ID: <8760dwrtqd.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <508034ae-e254-d0bd-5ca9-c3f1959f8fe5@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1196 bytes --]
Recent patch to description of MNT_FORCE incorrectly
dropped the mention of possible data loss. Restore it.
Signed-off-by: NeilBrown <neilb@suse.com>
---
Sorry, I thought I had put the mention of data loss back it, but clearly
not.
NeilBrown
man2/umount.2 | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/man2/umount.2 b/man2/umount.2
index ccd1d07afe88..01f42710ee9d 100644
--- a/man2/umount.2
+++ b/man2/umount.2
@@ -63,9 +63,10 @@ controlling the behavior of the operation:
.BR MNT_FORCE " (since Linux 2.1.116)"
Ask the filesystem to abort pending requests before attempting the
unmount. This may allow the unmount to complete without waiting
-for an inaccessible server. If, after aborting requests, some
-processes still have active references to the filesystem, the
-unmount will still fail. In Linux 4.12, only the filesystems
+for an inaccessible server, but could cause data loss. If, after
+aborting requests, some processes still have active references to the
+filesystem, the unmount will still fail. In Linux 4.12, only the
+filesystems
9p (2.6.16),
ceph (2.6.34),
cifs (2.6.12),
--
2.14.0.rc0.dirty
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2017-08-10 3:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-08 5:49 [PATCH manpages] umount.2: revise MNT_FORCE description NeilBrown
[not found] ` <87mv7asj5l.fsf-wvvUuzkyo1HefUI2i7LXDhCRmIWqnp/j@public.gmane.org>
2017-08-08 19:26 ` Michael Kerrisk (man-pages)
2017-08-10 3:23 ` NeilBrown [this message]
2017-08-12 20:07 ` [PATCH manpages] umount.2: restore mention of data loss with MNT_FORCE Michael Kerrisk (man-pages)
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=8760dwrtqd.fsf@notabene.neil.brown.name \
--to=neilb@suse.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.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