>> The result from a call of the function “kasprintf” was passed to >> a subsequent function call without checking for a null pointer before >> (according to a memory allocation failure). >> This issue was detected by using the Coccinelle software. > > This is correct and I'm fine with the patch if it avoids ringing alarm > bells somewhere, yet it doesn't fix an actual issue here since the > allocated buffer is merely passed to vsnprintf() which detects and > sanitizes %s args being NULL. Should null pointer tolerance be better indicated for such use cases by any additional means? Regards, Markus
