Created attachment 744009 [details] the browseable html report of the clang analysis on glusterfs I ran the the llvm/clang static source code analyzer on glusterfs (git master 'git://forge.gluster.org/glusterfs-core/glusterfs.git') (git commit: Thu May 2, 2013). The attachment is the complete browseable html report.
Updated the 'url' to point to the browseable html code coverage report.
Updated the 'url'
Created attachment 753754 [details] screen shot of important errors Only the errors ticked in the box shown above needs to be addressed, and out of that, we can't ideally make changes to 'contrib/' directory, so consider making changes to all other files.
All the security errors are coming in from contrib and they have no bearing in glusterfs context. Hence we can ignore the security warnings in this clang report.
Out of curiosity, the contrib/ code errors seem to be in the fuse stuff we're carrying. Does anything get compiled from that contrib/ code then distributed by us?