[lkml]   [2002]   [Jul]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: lock_kernel check...
dan carpenter wrote:
> is from the scripts page. Smatch is a
> really unfinished code checker that I've been working on. It is
> based on reading the papers about the Stanford checker.

There was a time when I was thinking about the same thing. It kept
scaring me the more I thought about it.

> Unfortunately, after a night of sleep I realize that my script is
> broken for 2 reasons. 1) is meant to track state changes
> down different code paths. But unfortunately it wasn't doing that
> in this case; it was just going down the code without taking into
> consideration any if_stmts etc. I'm extremely embarassed about
> that. Sorry.

Don't be sorry. The script is smarter than the people who caused the
errors. (once again, probably me)

> 2) What the Stanford checker does is print an error
> if one return_stmt is called while the kernel is locked and one is
> called while the kernel is unlocked. This seems reasonable.

Could you clarify that a bit?

> I will fix both mistakes later on this week. Unfortunately I'm in
> the process of moving and looking for a job etc so I might not get
> to it for a bit.

Dave Hansen

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:22    [W:0.035 / U:2.992 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site