From: Mark Tinguely <tinguely@sgi.com>
To: xfs@oss.sgi.com
Subject: [PATCH] xfsrestore: fix string corruption in shrink()
Date: Thu, 13 Nov 2014 13:14:45 -0600 [thread overview]
Message-ID: <20141113191510.176392492@sgi.com> (raw)
[-- Attachment #1: xfsrestore-fix-string-corruption-in-shrink.patch --]
[-- Type: text/plain, Size: 1402 bytes --]
Linux strcpy() corrupts the output string when the input
and output strings overlap. The shrink() function in xfsrestore
uses an overlapping strcpy() to remove special characters when
processing an interactive command line. The resultant command
will fail.
examples:
-> cd "AOGC exome chip core genotyping"
AOGC exome chp core genotyping not found
-> cd "t t"
tt not found
Fix my manually moving the characters in the array.
Signed-off-by: Mark Tinguely <tinguely@sgi.com>
---
restore/tree.c | 14 +++++++++++++-
1 file changed, 13 insertions(+), 1 deletion(-)
Index: b/restore/tree.c
===================================================================
--- a/restore/tree.c
+++ b/restore/tree.c
@@ -4857,7 +4857,19 @@ distance_to_space( char *s, char *l )
static void
shrink( char *s, size_t cnt )
{
- strcpy( s, s + cnt );
+ /*
+ * Linux strcpy corrupts the string if the src and dst overlap.
+ * Manually copy the entries to the left.
+ *
+ * Since the liter array is mostly nulls, shrink is not moving
+ * the array left as intended. Does not seem to be many embedded
+ * processing characters, so leaving it for now
+ */
+ char *m = s + cnt;
+ while (*m != '\0')
+ *s++ = *m++;
+ /* NULL the last character of the string */
+ *s = '\0';
}
static int
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2014-11-13 19:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-13 19:14 Mark Tinguely [this message]
2014-11-13 19:41 ` [PATCH] xfsrestore: fix string corruption in shrink() Eric Sandeen
2014-11-13 19:56 ` Mark Tinguely
2014-11-13 20:45 ` Eric Sandeen
2014-11-13 21:57 ` Mark Tinguely
2014-11-13 21:50 ` Dave Chinner
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=20141113191510.176392492@sgi.com \
--to=tinguely@sgi.com \
--cc=xfs@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox