summaryrefslogtreecommitdiff
path: root/arch/microblaze
diff options
context:
space:
mode:
authorChris Metcalf <cmetcalf@ezchip.com>2015-04-29 12:52:04 -0400
committerChris Metcalf <cmetcalf@ezchip.com>2015-09-10 15:36:59 -0400
commit30035e45753b708e7d47a98398500ca005e02b86 (patch)
treea7a03ae69c14176c9824a382b0eef09cf8687c8b /arch/microblaze
parenta6e2f029ae34f41adb6ae3812c32c5d326e1abd2 (diff)
downloadlinux-sh-30035e45753b708e7d47a98398500ca005e02b86.tar.gz
string: provide strscpy()
The strscpy() API is intended to be used instead of strlcpy(), and instead of most uses of strncpy(). - Unlike strlcpy(), it doesn't read from memory beyond (src + size). - Unlike strlcpy() or strncpy(), the API provides an easy way to check for destination buffer overflow: an -E2BIG error return value. - The provided implementation is robust in the face of the source buffer being asynchronously changed during the copy, unlike the current implementation of strlcpy(). - Unlike strncpy(), the destination buffer will be NUL-terminated if the string in the source buffer is too long. - Also unlike strncpy(), the destination buffer will not be updated beyond the NUL termination, avoiding strncpy's behavior of zeroing the entire tail end of the destination buffer. (A memset() after the strscpy() can be used if this behavior is desired.) - The implementation should be reasonably performant on all platforms since it uses the asm/word-at-a-time.h API rather than simple byte copy. Kernel-to-kernel string copy is not considered to be performance critical in any case. Signed-off-by: Chris Metcalf <cmetcalf@ezchip.com>
Diffstat (limited to 'arch/microblaze')
0 files changed, 0 insertions, 0 deletions