All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Arlott <simon@octiron.net>
To: linux-cifs@vger.kernel.org
Subject: [PATCH] Add missing position handling to mount parameters gid/backup_gid/snapshot
Date: Thu, 26 Nov 2020 00:28:08 +0000	[thread overview]
Message-ID: <2991484d-15b9-a846-565f-e86ccb83768d@0882a8b5-c6c3-11e9-b005-00805fc181fe> (raw)

The code tries to optimise for the last parameter not needing to update
the position which means that every time a new one is added to the end
by copying and pasting, the string position is not updated.

That makes it impossible to use backup_uid=/backup_gid=/snapshot= after
gid= or snapshot= after backup_gid= because part of the string is
overwritten and contains invalid keys like "gbackup_uid".

Prepare for the next parameter to be added on the end by updating the
position for snapshot= even though it will be unused.
---
 mount.cifs.c | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/mount.cifs.c b/mount.cifs.c
index 4feb397..a169bc6 100644
--- a/mount.cifs.c
+++ b/mount.cifs.c
@@ -1229,6 +1229,7 @@ nocopy:
 			out_len++;
 		}
 		snprintf(out + out_len, word_len + 5, "gid=%s", txtbuf);
+		out_len = strlen(out);
 	}
 	if (got_bkupuid) {
 		word_len = snprintf(txtbuf, sizeof(txtbuf), "%u", bkupuid);
@@ -1260,6 +1261,7 @@ nocopy:
 			out_len++;
 		}
 		snprintf(out + out_len, word_len + 11, "backupgid=%s", txtbuf);
+		out_len = strlen(out);
 	}
 	if (got_snapshot) {
 		word_len = snprintf(txtbuf, sizeof(txtbuf), "%llu", snapshot);
@@ -1275,6 +1277,7 @@ nocopy:
 			out_len++;
 		}
 		snprintf(out + out_len, word_len + 11, "snapshot=%s", txtbuf);
+		out_len = strlen(out);
 	}
 
 	return 0;
-- 
2.17.1

-- 
Simon Arlott

             reply	other threads:[~2020-11-26  0:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-26  0:28 Simon Arlott [this message]
2020-12-09 19:33 ` [PATCH] Add missing position handling to mount parameters gid/backup_gid/snapshot Pavel Shilovsky

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=2991484d-15b9-a846-565f-e86ccb83768d@0882a8b5-c6c3-11e9-b005-00805fc181fe \
    --to=simon@octiron.net \
    --cc=linux-cifs@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 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.