Blame SOURCES/0157-losetup-add-info-about-lazy-detach-to-manpage.patch

ad9577
From 0258872e2b45b589481e6796aa983f8749be9ada Mon Sep 17 00:00:00 2001
ad9577
From: Karel Zak <kzak@redhat.com>
ad9577
Date: Thu, 10 Aug 2017 12:37:34 +0200
ad9577
Subject: [PATCH 157/173] losetup: add info about lazy detach to manpage
ad9577
ad9577
Upstream: http://github.com/karelzak/util-linux/commit/60eedb0a53f14aa1169713a72325421db8e1c647
ad9577
Addresses: http://bugzilla.redhat.com/show_bug.cgi?id=1566390
ad9577
Signed-off-by: Karel Zak <kzak@redhat.com>
ad9577
---
ad9577
 sys-utils/losetup.8 | 5 ++++-
ad9577
 1 file changed, 4 insertions(+), 1 deletion(-)
ad9577
ad9577
diff --git a/sys-utils/losetup.8 b/sys-utils/losetup.8
ad9577
index 9a8c1d597..45c220187 100644
ad9577
--- a/sys-utils/losetup.8
ad9577
+++ b/sys-utils/losetup.8
ad9577
@@ -80,7 +80,10 @@ without --list) is deprecated.
ad9577
 .IP "\fB\-c, \-\-set-capacity\fP \fIloopdev\fP
ad9577
 force loop driver to reread size of the file associated with the specified loop device
ad9577
 .IP "\fB\-d, \-\-detach\fP \fIloopdev\fP..."
ad9577
-detach the file or device associated with the specified loop device(s)
ad9577
+detach the file or device associated with the specified loop device(s). Note
ad9577
+that since Linux v3.7 kernel uses "lazy device destruction".  The detach
ad9577
+operation does not return EBUSY error anymore if device is actively used by
ad9577
+system, but it is marked by autoclear flag and destroyed later.
ad9577
 .IP "\fB\-D, \-\-detach-all\fP"
ad9577
 detach all associated loop devices
ad9577
 .IP "\fB\-f, \-\-find\fP"
ad9577
-- 
ad9577
2.14.4
ad9577