> The problem is the __must_check does not mean that the > return value must be followed by a comparison to NULL and bailing out > (that can't really be checked), it simply ensures the return value is > assigned somewhere or used in an if(). So foo->bar = kstrdup() not > followed by a check of foo->bar won't warn. Higher level source code analysis tools like the semantic patch language (Coccinelle software) can help to find such missing checks. Would you like to point any additional development tools out for this purpose? Regards, Markus
