Hi Sakari cc: adding Greg (core and FormatGuard) and Chistopher (sparse) > > I just realised there was another issue --- the name is now interpreted as > format string. Bad things will happen if there's e.g. %s in the name itself > --- perhaps unlikely, but possible.
Good catch! Would it be possible to add a sparse check to avoid this in all the kernel? And what about a macro protection like FormatGuard? https://www.usenix.org/legacy/events/sec01/full_papers/cowanbarringer/cowanbarringer.pdf Thanks! -- Ricardo Ribalda -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
