Benno Schulenberg wrote: > Hmm... How come that it doesn't flag the very similar segment in > static inline void cpuid(...) as suspicious? Is it the 'inl' command? > (What does this do anyway? It isn't an x86 assembly that I can find.) The IN does a read from I/O port space; the "l" suffix in AT&T syntax means 32-bit operand size. I'm guessing AddressSanitizer sees what looks like a memory reference with 16-bit address size coming from nowhere that should have a pointer in it and complains. It's not a "real" memory reference, so ignoring the whole function seems reasonable. (It's very unusual to use that instruction from userspace, so it's not surprising it wouldn't be recognized.) ---> Drake Wilson -- To unsubscribe from this list: send the line "unsubscribe util-linux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
