summaryrefslogtreecommitdiffstats
path: root/xlators/features/marker/src
diff options
context:
space:
mode:
Diffstat (limited to 'xlators/features/marker/src')
-rw-r--r--xlators/features/marker/src/marker-quota.c4
-rw-r--r--xlators/features/marker/src/marker.c4
2 files changed, 4 insertions, 4 deletions
diff --git a/xlators/features/marker/src/marker-quota.c b/xlators/features/marker/src/marker-quota.c
index b6bf2fb36a4..06ba0820a54 100644
--- a/xlators/features/marker/src/marker-quota.c
+++ b/xlators/features/marker/src/marker-quota.c
@@ -1325,7 +1325,7 @@ mq_reduce_parent_size_task (void *opaque)
locked = _gf_true;
if (contri.size >= 0) {
- /* contri paramater is supplied only for rename operation.
+ /* contri parameter is supplied only for rename operation.
* remove xattr is alreday performed, we need to skip
* removexattr for rename operation
*/
@@ -1554,7 +1554,7 @@ mq_initiate_quota_task (void *opaque)
Suppose hard link for a file f1 present in a directory d1 is
created in the directory d2 (as f2). Now, since d2's
contribution is not there in f1's inode ctx, d2's
- contribution xattr wont be created and will create problems
+ contribution xattr won't be created and will create problems
for quota operations.
Don't create contribution if parent has been changed after
diff --git a/xlators/features/marker/src/marker.c b/xlators/features/marker/src/marker.c
index 659ca890066..522fdfb86d1 100644
--- a/xlators/features/marker/src/marker.c
+++ b/xlators/features/marker/src/marker.c
@@ -1364,7 +1364,7 @@ marker_rename_unwind (call_frame_t *frame, void *cookie, xlator_t *this,
if (local->stub != NULL) {
/* Remove contribution node from in-memory even if
* remove-xattr has failed as the rename is already performed
- * if local->stub is set, which means rename was sucessful
+ * if local->stub is set, which means rename was successful
*/
(void) mq_inode_ctx_get (oplocal->loc.inode, this, &ctx);
if (ctx) {
@@ -1641,7 +1641,7 @@ err:
* b) we should subtract from src-parent exactly what we contributed to
* src-parent
* So, We hold a lock on src-parent to block any parallel transcations on
- * src-inode (since thats the one which survives rename).
+ * src-inode (since that's the one which survives rename).
*
* If there are any parallel transactions on dst-inode they keep succeeding
* till the association of dst-inode with dst-parent is broken because of an