On 08/10/2017 05:23 AM, NeilBrown wrote: > > Recent patch to description of MNT_FORCE incorrectly > dropped the mention of possible data loss. Restore it. > > Signed-off-by: NeilBrown <neilb@xxxxxxxx> > --- > > Sorry, I thought I had put the mention of data loss back it, but clearly > not. Thanks, Neil. Applied. Cheers, Michael > 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), > -- Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ Linux/UNIX System Programming Training: http://man7.org/training/ -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
