<p><br>
On Jun 22, 2012 7:14 AM, "Dan Carpenter" <<a href="mailto:dan.carpenter@oracle.com">dan.carpenter@oracle.com</a>> wrote:<br>
><br>
> I'm coming late to the discussion. Guenter Roeck mentioned static<br>
> checking in a previous message:<br>
> <a href="http://lists.linux-foundation.org/pipermail/ksummit-2012-discuss/2012-June/000166.html">http://lists.linux-foundation.org/pipermail/ksummit-2012-discuss/2012-June/000166.html</a><br>
><br>
> Smatch actually found the bug mentioned in the email.<br>
><br>
> I go through Smatch warnings for every linux-next release. Starting<br>
> from the last kernel summit I would have emailed the submitter and<br>
> the OCFS list. Even back in May 2011 I probably would have fixed<br>
> the bug except that my laptop had just been stolen a few weeks prior<br>
> and I was unemployed. These days I'm rolling in cash and laptops so<br>
> I'm confident I would have reported it.<br>
></p>
<p>Would it make sense to give talk/session about the ways one can screw up the code unintentionally- so that folks who review patches remember to check for that? This way we can be better about not submitting code that has those issues and I hope become better engineers.</p>