On Mon, Feb 12, 2007 at 07:50:24AM -0800, Linus Torvalds wrote: > > Now, you can either try to make sparsedo global analysis (which some > people apparently really _are_ trying to do), or you can tell sparse that > it holds a certain lock on entry, and is _supposed_ to release it. You can > do that by annotating the function with __acquires/__releases(): > > int myfunction(..) > __releases(kernel_lock) > __acquires(kernel_lock) Aha. That is the purpose of ctype member "context_list *context". I was puzzling about it when I am reading the context checking code. Without knowing the input/output context stuff, this syntax is really cryptic. # define __acquire(x) __context__(x,1) # define __acquires(x) __attribute__((context(x,0,1))) # define __releases(x) __attribute__((context(x,1,0))) > - it shows the *programmer* that the function is doing somethign > "strange" (not really strange, but still: it's basically a fairly > readable way that it's doing locking in a weird way). Should the function declare in the header file has that as well? When call one of those functions, it can know that function will change context. That might be a way to solve the problem that some of the spinlock function is not a inline function at all. Chris - 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
