diff --git a/Documentation/device-mapper/dm-log.txt b/Documentation/device-mapper/dm-log.txt index 994dd75475a63a851809c00f972b9c2bbdfba8e1..c155ac569c440b49c336d763a3ca30d25afde9db 100644 --- a/Documentation/device-mapper/dm-log.txt +++ b/Documentation/device-mapper/dm-log.txt @@ -48,7 +48,7 @@ kernel and userspace, 'connector' is used as the interface for 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. diff --git a/drivers/md/dm-log-userspace-base.c b/drivers/md/dm-log-userspace-base.c index 1021c89860116a5bb6e3a2faea1362c0ea805f52..3c27978890b7651542c7a3498faa371b557dfd9b 100644 --- a/drivers/md/dm-log-userspace-base.c +++ b/drivers/md/dm-log-userspace-base.c @@ -146,7 +146,7 @@ static int build_constructor_string(struct dm_target *ti, * * Where 'other args' is the userspace implementation specific log * arguments. An example might be: - * clustered_disk [[no]sync] + * clustered-disk [[no]sync] * * So, this module will strip off the for identification purposes * when communicating with userspace about a log; but will pass on everything