Static Analysis by Dan Carpenter

People say that it’s a red flag when a function has “simple” in the name and that’s true for the simple_write_to_buffer() function, for sure.

You have probably been directed here because someone suspects you have sent AI Slop.

I’ve previously blogged about how to write error handling.

LWN recently had an article about a buffer overflow in Rsync.

I gave a talk at Linaro Connect about static analysis in the kernel.

TL/DR; Smatch has a warning “warn: sleeping in atomic context”.

There are a lot of people who write “return ret;” when they mean “return 0;” I feel like I’m the person who cares about this the most in the world, but hopefully after reading this blog you will notice it as well and it will annoy you.

This is no longer a debate in the Linux kernel, but I saw some code written in out of date style recently and it was a moment of reminiscing.

The kernel has a number of strcpy() functions that copy a string from one pointer to another.

I really believe in static checkers but sometimes static checker advice is wrong and harmful.