On Fri, 2007-03-30 at 17:26 -0700, Suhabe Bugrara wrote: > 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? I suggest that we check what we can. The priority should be given to whatever check finds most (and/or worst) errors with minimal annotation. I wish we could have rules mandating certain locks to be held when some data is accessed, but there should be an exception for initialization stage, when the data is being populated. > Could locking errors > in the kernel be potentially more serious than dereferencing an > unchecked user pointer for example? It's hard to compare seriousness. Lockups are normally treated as less serious bugs than unauthorized access. On the other hand unauthorized access rarely leads to anything more serious than embarrassment and monetary loss, whereas lockups could lead to life loss, even if the equipment is not connected to the network. Think of airplanes losing control, unexploded munitions, life support equipment stopping when it's most needed etc. -- Regards, Pavel Roskin - 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
