On Thu, 2007-03-01 at 6:07:06, Pavel Roskin wrote:
Moreover, I think that incorrect use of locking is a remaining major issue not covered by sparse.
Hello, What particular locking usage rules would Sparse ideally check? I guess this would include finding double locking/unlocking errors. Are there other more important locking usage rules? Could locking errors in the kernel be potentially more serious than dereferencing an unchecked user pointer for example? Suhabe - To unsubscribe from this list: send the line "unsubscribe linux-sparse" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
