From: Kevin Corry <kevcorry@us.ibm.com>
To: LKML <linux-kernel@vger.kernel.org>, Andrew Morton <akpm@osdl.org>
Subject: [PATCH] Device-Mapper 0/9
Date: Mon, 12 Apr 2004 09:12:45 -0500 [thread overview]
Message-ID: <200404120912.45870.kevcorry@us.ibm.com> (raw)
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.
next reply other threads:[~2004-04-12 14:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-12 14:12 Kevin Corry [this message]
2004-04-12 14:18 ` [PATCH] Device-Mapper 1/9 Kevin Corry
2004-04-12 14:18 ` [PATCH] Device-Mapper 2/9 Kevin Corry
2004-04-12 14:18 ` [PATCH] Device-Mapper 3/9 Kevin Corry
2004-04-12 14:18 ` [PATCH] Device-Mapper 4/9 Kevin Corry
2004-04-12 14:18 ` [PATCH] Device-Mapper 5/9 Kevin Corry
2004-04-12 14:18 ` [PATCH] Device-Mapper 6/9 Kevin Corry
2004-04-12 14:19 ` [PATCH] Device-Mapper 7/9 Kevin Corry
2004-04-12 14:19 ` [PATCH] Device-Mapper 8/9 Kevin Corry
2004-04-12 14:19 ` [PATCH] Device-Mapper 9/9 Kevin Corry
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200404120912.45870.kevcorry@us.ibm.com \
--to=kevcorry@us.ibm.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®