Hi, I'm trying to write a type checker for the kernel's %p format extensions, but I've run into a problem with sparse which I can't debug myself. It seems that something goes wrong when sparse is concatenating literal strings, one of which was hidden behind a macro. As a random example, drivers/net/ethernet/realtek/atp.c:471 has this format string: KERN_DEBUG "%s: Reset: current Rx mode %d.\n" KERN_DEBUG ultimately expands to "\001" "7". When I print the corresponding ->string->data, I get ^A6%s7%s: Reset: current Rx mode %d. (^A is just less' way of showing the \001 byte - that part is fine). Note the extra "6%s". Needless to say, such random extra content makes format string verification very hard... If I replace KERN_DEBUG by its expansion "\001" "7", it works fine. If I only replace it by its immediate replacement KERN_SOH "7", I see the same bad behaviour. Any ideas? Rasmus -- To unsubscribe from this list: send the line "unsubscribe linux-sparse" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
