* [PATCH v2] block/loop: add documentation for sysfs interface
@ 2018-02-17 6:13 Aishwarya Pant
2018-02-23 15:20 ` Jonathan Corbet
0 siblings, 1 reply; 2+ messages in thread
From: Aishwarya Pant @ 2018-02-17 6:13 UTC (permalink / raw)
To: linux-block
Cc: Julia Lawall, linux-kernel, Jonathan Corbet, Greg KH, linux-doc
Documentation has been compiled from git logs and by reading through
code.
Signed-off-by: Aishwarya Pant <aishpant@gmail.com>
---
For drivers/block/loop.c, I don't see any maintainers or mailing lists except
for LKML. I am guessing linux-block mailing list should be okay.
Changes in v2:
- Add linux-block@vger.kernel.org to the recipient list.
Documentation/ABI/testing/sysfs-block-loop | 50 ++++++++++++++++++++++++++++++
1 file changed, 50 insertions(+)
create mode 100644 Documentation/ABI/testing/sysfs-block-loop
diff --git a/Documentation/ABI/testing/sysfs-block-loop b/Documentation/ABI/testing/sysfs-block-loop
new file mode 100644
index 000000000000..627f4eb87286
--- /dev/null
+++ b/Documentation/ABI/testing/sysfs-block-loop
@@ -0,0 +1,50 @@
+What: /sys/block/loopX/loop/autoclear
+Date: Aug, 2010
+KernelVersion: v2.6.37
+Contact: linux-block@vger.kernel.org
+Description:
+ (RO) Shows if the device is in autoclear mode or not ( "1" or
+ "0"). Autoclear (if set) indicates that the loopback device will
+ self-distruct after last close.
+
+What: /sys/block/loopX/loop/backing_file
+Date: Aug, 2010
+KernelVersion: v2.6.37
+Contact: linux-block@vger.kernel.org
+Description:
+ (RO) The path of the backing file that the loop device maps its
+ data blocks to.
+
+What: /sys/block/loopX/loop/offset
+Date: Aug, 2010
+KernelVersion: v2.6.37
+Contact: linux-block@vger.kernel.org
+Description:
+ (RO) Start offset (in bytes).
+
+What: /sys/block/loopX/loop/sizelimit
+Date: Aug, 2010
+KernelVersion: v2.6.37
+Contact: linux-block@vger.kernel.org
+Description:
+ (RO) The size (in bytes) that the block device maps, starting
+ from the offset.
+
+What: /sys/block/loopX/loop/partscan
+Date: Aug, 2011
+KernelVersion: v3.10
+Contact: linux-block@vger.kernel.org
+Description:
+ (RO) Shows if automatic partition scanning is enabled for the
+ device or not ("1" or "0"). This can be requested individually
+ per loop device during its setup by setting LO_FLAGS_PARTSCAN in
+ in the ioctl request. By default, no partition tables are
+ scanned.
+
+What: /sys/block/loopX/loop/dio
+Date: Aug, 2015
+KernelVersion: v4.10
+Contact: linux-block@vger.kernel.org
+Description:
+ (RO) Shows if direct IO is being used to access backing file or
+ not ("1 or "0").
--
2.16.1
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH v2] block/loop: add documentation for sysfs interface
2018-02-17 6:13 [PATCH v2] block/loop: add documentation for sysfs interface Aishwarya Pant
@ 2018-02-23 15:20 ` Jonathan Corbet
0 siblings, 0 replies; 2+ messages in thread
From: Jonathan Corbet @ 2018-02-23 15:20 UTC (permalink / raw)
To: Aishwarya Pant
Cc: linux-block, Julia Lawall, linux-kernel, Greg KH, linux-doc
On Sat, 17 Feb 2018 11:43:04 +0530
Aishwarya Pant <aishpant@gmail.com> wrote:
> Documentation has been compiled from git logs and by reading through
> code.
>
> Signed-off-by: Aishwarya Pant <aishpant@gmail.com>
> ---
> For drivers/block/loop.c, I don't see any maintainers or mailing lists except
> for LKML. I am guessing linux-block mailing list should be okay.
>
> Changes in v2:
> - Add linux-block@vger.kernel.org to the recipient list.
Applied to the docs tree, thanks.
jon
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2018-02-23 15:20 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-02-17 6:13 [PATCH v2] block/loop: add documentation for sysfs interface Aishwarya Pant
2018-02-23 15:20 ` Jonathan Corbet
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).