[<prev] [next>] [day] [month] [year] [list]
Message-Id: <AA265B63-A9D7-4A21-A279-88894DEF46C4@cam.ac.uk>
Date: Tue, 12 Jun 2012 23:32:40 +0100
From: Anton Altaparmakov <aia21@....ac.uk>
To: Steve French <sfrench@...ba.org>
Cc: linux-cifs@...r.kernel.org, samba-technical@...ts.samba.org,
LKML <linux-kernel@...r.kernel.org>
Subject: Patch: Fix return value in cifsConvertToUTF16().
Hi,
Please apply the below patch which fixes the return value in cifsConvertToUTF16(). At the moment it is returning the number of bytes in the input string which is not the same as returning the number of returned UTF16 characters! (Note the mount is done using "iocharset=utf8".)
This causes rename system call with source being a Unicode name to fail because in UTF8 the unicode characters are more than one byte long thus cifsConvertToUTF16() returns a number larger than the actual number of returned UTF16 characters thus CIFSSMBRename() ends up constructing one or more NULL characters at the end of the source filename thus it sends a rename command like this to the server: "source_name\0 target_name" which the server presumably interprets as just "source_name" which is obviously bogus for a rename call and thus the rename fails.
The simple and obviously correct fix is the below patch which changes the cifsConvertToUTF16() function to return variable "j" instead of "i" which is the index into the destination UTF16 array which is the correct thing to do and fixes the rename bug.
Signed-off-by: Anton Altaparmakov <aia21@....ac.uk>
Best regards,
Anton
--
Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @)
Unix Support, Computing Service, University of Cambridge, CB2 3QH, UK
Linux NTFS maintainer, http://www.linux-ntfs.org/
---
diff --git a/fs/cifs/cifs_unicode.c b/fs/cifs/cifs_unicode.c
index fbb9da9..33ef60d 100644
--- a/fs/cifs/cifs_unicode.c
+++ b/fs/cifs/cifs_unicode.c
@@ -328,6 +328,6 @@ cifsConvertToUTF16(__le16 *target, const char *source, int s
}
ctoUTF16_out:
- return i;
+ return j;
}
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists