Hi Walter
ok, i understand now (i hope).
maybe this version is more clear:
The LOOP_SET_STATUS can neither set the
.B lo_flags
LO_FLAGS_READ_ONLY nor the LO_FLAGS_DIRECT_IO
because they are exclusively set from kernel.
Sorry for the late reply.
I think it is better.
Thanks.
Let's wait for Michael's review.
Best Regards
Yang Xu
hope that helps
wh
________________________________________
Von: linux-man-owner@xxxxxxxxxxxxxxx [linux-man-owner@xxxxxxxxxxxxxxx] im Auftrag von Yang Xu [xuyang2018.jy@xxxxxxxxxxxxxx]
Gesendet: Montag, 10. August 2020 08:53
An: Walter Harms; linux-man@xxxxxxxxxxxxxxx
Betreff: Re: AW: [PATCH v2 2/3] loop.4: add some details about lo_flag
Hi Walter
Hi,
IMHO "first" and "last" is something that should be avoided in documentation
because the meaning may change in future releases.
Thanks, I see.
I guess you want to say: lo_number and reserved ?
No, I just said the loop_set_status ioctl can not set read-only and
direct io flag.
Best Regards
Yang Xu
re,
wh
________________________________________
Von: linux-man-owner@xxxxxxxxxxxxxxx [linux-man-owner@xxxxxxxxxxxxxxx] im Auftrag von Yang Xu [xuyang2018.jy@xxxxxxxxxxxxxx]
Gesendet: Donnerstag, 6. August 2020 11:48
An: linux-man@xxxxxxxxxxxxxxx
Cc: Yang Xu
Betreff: [PATCH v2 2/3] loop.4: add some details about lo_flag
Signed-off-by: Yang Xu <xuyang2018.jy@xxxxxxxxxxxxxx>
---
man4/loop.4 | 3 +++
1 file changed, 3 insertions(+)
diff --git a/man4/loop.4 b/man4/loop.4
index 1f8a31ac7..41abe0122 100644
--- a/man4/loop.4
+++ b/man4/loop.4
@@ -136,6 +136,9 @@ Allow automatic partition scanning.
Use direct io mode to access backing file.
.RE
.TP
+.I The LOOP_SET_STATUS can not set the first and last flag because
+they are both set from kernel.
+.TP
.B LOOP_GET_STATUS
Get the status of the loop device.
The (third)
--
2.23.0
