Linus Torvalds <torvalds@xxxxxxxx> writes: > it's entirely possible that it will load bytes from "string" _past_ the > end of the string because of an unrolled inner loop that does things > multiple bytes at a time. They won't be used in the eventual result, but > just the fact that they are loaded from memory can mean that your program > takes a SIGSEGV, for example, becaue it turns out "string" was just a > single NUL byte at the end of a page, and there's nothing after it. Funny. I've seen this exact bug in memcmp and strcmp in earlier SunOS (pre Solaris) libc when I was working on something like Valgrind in my previous life. - : send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html