Re: busy loops in kernel

Asim
2012-01-18T17:48:12Z

Hi Dan,

Yes we do static analysis. The txt file has a bit more information. It
is actually: count, line numbers and C file. In some cases, when
driver comprises of multiple files, line numbers may be shifted (since
all files are merged together for analysis).

Some cases are more insidious where drivers use hardware values for
array/pointer de-reference. They are way fewer than busy loops but I
have muted them for this iteration at least.

And, yes these are real infinite loops, about 1000 of them.

Thanks,
Asim

On Tue, Jan 17, 2012 at 11:37 PM, Dan Carpenter
<dan.carpenter@oracle.com> wrote:
> Interesting stuff.  You guys are doing static analysis on the .o
> files?  I'm looking at the first line.
>
> ticks 25 What does the ticks count mean?
>
> Infinite Loop:142  Ok.  I see this on drivers/atm/zatm.c line 142.
> It's a real infinite loop (if you're zatm hardware is broken).
>
> Dynamic array:393  What's this?  I don't see any dynamic arrays in
> this driver.
>
> regards,
> dan carpenter
>
--
To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html