[PATCH] Device-Mapper 7/9
From: Kevin Corry (kevcorry_at_us.ibm.com)
Date: 04/12/04
- Previous message: Kevin Corry: "[PATCH] Device-Mapper 5/9"
- In reply to: Kevin Corry: "[PATCH] Device-Mapper 0/9"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
To: LKML <linux-kernel@vger.kernel.org>, Andrew Morton <akpm@osdl.org> Date: Mon, 12 Apr 2004 09:19:07 -0500
Clarify the comment regarding the "next" field in struct dm_target_spec. The
"next" field has different behavior if you're performing a DM_TABLE_STATUS
command than it does if you're performing a DM_TABLE_LOAD command.
See populate_table() and retrieve_status() in drivers/md/dm-ioctl.c for more
details on how this field is used.
--- diff/include/linux/dm-ioctl.h 2004-04-09 09:41:45.000000000 -0500
+++ source/include/linux/dm-ioctl.h 2004-04-09 09:42:36.000000000 -0500
@@ -129,8 +129,14 @@
int32_t status; /* used when reading from kernel only */
/*
- * Offset in bytes (from the start of this struct) to
- * next target_spec.
+ * Location of the next dm_target_spec.
+ * - When specifying targets on a DM_TABLE_LOAD command, this value is
+ * the number of bytes from the start of the "current" dm_target_spec
+ * to the start of the "next" dm_target_spec.
+ * - When retrieving targets on a DM_TABLE_STATUS command, this value
+ * is the number of bytes from the start of the first dm_target_spec
+ * (that follows the dm_ioctl struct) to the start of the "next"
+ * dm_target_spec.
*/
uint32_t next;
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Previous message: Kevin Corry: "[PATCH] Device-Mapper 5/9"
- In reply to: Kevin Corry: "[PATCH] Device-Mapper 0/9"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
