From: Jonathan Brassow <jbrassow@redhat.com>
To: dm-devel@redhat.com
Subject: [PATCH 1 of 2] DM log userspace: Minor fix-ups
Date: Thu, 13 Oct 2011 14:16:34 -0500 [thread overview]
Message-ID: <1318533394.28595.6.camel@f14.redhat.com> (raw)
In-Reply-To: <1318533312.28595.4.camel@f14.redhat.com>
dm-log-userspace: use kzalloc instead of kmalloc (plus some comment fixes)
Signed-off-by: Jonathan Brassow <jbrassow@redhat.com>
Index: linux-upstream/drivers/md/dm-log-userspace-base.c
===================================================================
--- linux-upstream.orig/drivers/md/dm-log-userspace-base.c
+++ linux-upstream/drivers/md/dm-log-userspace-base.c
@@ -146,7 +146,7 @@ static int build_constructor_string(stru
* <UUID> <other args>
* Where 'other args' is the userspace implementation specific log
* arguments. An example might be:
- * <UUID> clustered_disk <arg count> <log dev> <region_size> [[no]sync]
+ * <UUID> clustered-disk <arg count> <log dev> <region_size> [[no]sync]
*
* So, this module will strip off the <UUID> for identification purposes
* when communicating with userspace about a log; but will pass on everything
@@ -167,7 +167,7 @@ static int userspace_ctr(struct dm_dirty
return -EINVAL;
}
- lc = kmalloc(sizeof(*lc), GFP_KERNEL);
+ lc = kzalloc(sizeof(*lc), GFP_KERNEL);
if (!lc) {
DMWARN("Unable to allocate userspace log context.");
return -ENOMEM;
Index: linux-upstream/Documentation/device-mapper/dm-log.txt
===================================================================
--- linux-upstream.orig/Documentation/device-mapper/dm-log.txt
+++ linux-upstream/Documentation/device-mapper/dm-log.txt
@@ -48,7 +48,7 @@ kernel and userspace, 'connector' is use
communication.
There are currently two userspace log implementations that leverage this
-framework - "clustered_disk" and "clustered_core". These implementations
+framework - "clustered-disk" and "clustered-core". These implementations
provide a cluster-coherent log for shared-storage. Device-mapper mirroring
can be used in a shared-storage environment when the cluster log implementations
are employed.
next prev parent reply other threads:[~2011-10-13 19:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-13 19:15 [PATCH 0 of 2] DM log userspace: Allow DM_ULOG_CTR exchange to accept devices for register Jonathan Brassow
2011-10-13 19:16 ` Jonathan Brassow [this message]
2011-10-19 0:13 ` [PATCH 1 of 2] DM log userspace: Minor fix-ups Alasdair G Kergon
2011-10-13 19:20 ` [PATCH 2 of 2] DM log userspace: Allow CTR device response Jonathan Brassow
2011-10-19 21:02 ` [PATCH 1 of 2 - v2] DM log userspace: Minor fix-ups Jonathan Brassow
2011-10-19 21:04 ` [PATCH 2 of 2 - v2] DM log userspace: Allow CTR device response Jonathan Brassow
2011-10-20 19:52 ` [PATCH 2 of 2 - v3] DM log userspace: Allow CTR device respons Jonathan Brassow
2011-10-24 19:06 ` [PATCH 2 of 2 - v4] DM log userspace: Allow CTR devices response Jonathan Brassow
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=1318533394.28595.6.camel@f14.redhat.com \
--to=jbrassow@redhat.com \
--cc=dm-devel@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.