[PATCH] Device-Mapper 0/9
From: Kevin Corry (kevcorry_at_us.ibm.com)
Date: 04/12/04
- Previous message: Jin Suh: "[2.4.25] PCMCIA PCI: No IRQ for interrupt pin A and failed to allocate shared interrupt"
- Next in thread: Kevin Corry: "[PATCH] Device-Mapper 9/9"
- Reply: Kevin Corry: "[PATCH] Device-Mapper 9/9"
- Reply: Kevin Corry: "[PATCH] Device-Mapper 3/9"
- Reply: Kevin Corry: "[PATCH] Device-Mapper 2/9"
- Reply: Kevin Corry: "[PATCH] Device-Mapper 1/9"
- Reply: Kevin Corry: "[PATCH] Device-Mapper 4/9"
- Reply: Kevin Corry: "[PATCH] Device-Mapper 6/9"
- Reply: Kevin Corry: "[PATCH] Device-Mapper 8/9"
- Reply: Kevin Corry: "[PATCH] Device-Mapper 5/9"
- Reply: Kevin Corry: "[PATCH] Device-Mapper 7/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:12:45 -0500
Device-Mapper bug-fixes from the -udm tree.
-- Kevin Corry kevcorry@us.ibm.com http://evms.sourceforge.net/ Revision 1: Fix 64/32 bit ioctl problems. Revision 2: Check the uptodate flag in sub-bios to see if there was an error. [Mike Christie] Revision 3: Handle interrupts within suspend. Revision 4: dm.c: Use wake_up() rather than wake_up_interruptible() with the eventq. Revision 5: Log an error if the target has unknown target type, or zero length. Revision 6: Correctly align the dm_target_spec structures during retrieve_status(). Revision 7: 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. Revision 8: dm-ioctl.c::retrieve_status(): Prevent overrunning the ioctl buffer by making sure we don't call the target status routine with a buffer size limit of zero. [Kevin Corry, Alasdair Kergon] Revision 9: Striped: Use an EMIT macro in the status function. - 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: Jin Suh: "[2.4.25] PCMCIA PCI: No IRQ for interrupt pin A and failed to allocate shared interrupt"
- Next in thread: Kevin Corry: "[PATCH] Device-Mapper 9/9"
- Reply: Kevin Corry: "[PATCH] Device-Mapper 9/9"
- Reply: Kevin Corry: "[PATCH] Device-Mapper 3/9"
- Reply: Kevin Corry: "[PATCH] Device-Mapper 2/9"
- Reply: Kevin Corry: "[PATCH] Device-Mapper 1/9"
- Reply: Kevin Corry: "[PATCH] Device-Mapper 4/9"
- Reply: Kevin Corry: "[PATCH] Device-Mapper 6/9"
- Reply: Kevin Corry: "[PATCH] Device-Mapper 8/9"
- Reply: Kevin Corry: "[PATCH] Device-Mapper 5/9"
- Reply: Kevin Corry: "[PATCH] Device-Mapper 7/9"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]