Re: [PATCH] add mutex to fbdev for fb_mmap locking

[Linus Torvalds <torvalds@linux-foundation.org>]

On Sun, 31 May 2009, Krzysztof Helt wrote:
>  
>  static int atafb_get_fix(struct fb_fix_screeninfo *fix, struct fb_info *info)
> +__acquires(&info->mm_lock)
> +__releases(&info->mm_lock)

Btw, you shouldn't do this when things nest "correctly" - sparse will see 
the fact that the function acquires and releases a lock and is perfectly 
happy.

The extra annotations are helpful only if you have a function that does 
something _unexpected_ to a lock, like first releasing it and then 
re-aqcuiring it, or releasing it without acquiring it at all. Then the 
extra annotations (a) tell sparse not to complain about odd locking, and 
(b) act as visual notification to users that this function drops a lock in 
the middle.

I haven't actually looked at the patch yet, I just reacted to this part of 
it.

		Linus

------------------------------------------------------------------------------
Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT 
is a gathering of tech-side developers & brand creativity professionals. Meet
the minds behind Google Creative Lab, Visual Complexity, Processing, & 
iPhoneDevCamp as they present alongside digital heavyweights like Barbarian 
Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com