Bug 959887

Summary: clang static src analysis of glusterfs
Product: [Community] GlusterFS Reporter: John Smith <lbalbalba>
Component: buildAssignee: raghav <rpichai>
Status: CLOSED NOTABUG QA Contact:
Severity: medium Docs Contact:
Priority: high    
Version: mainlineCC: aavati, amarts, gluster-bugs, jahernan, jclift, kseifried, nsathyan, vbellur
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
URL: http://clang-scans.rhcloud.com/glusterfs/
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-06-30 15:33:48 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
the browseable html report of the clang analysis on glusterfs
none
screen shot of important errors none

Description John Smith 2013-05-06 07:59:42 UTC
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.

Comment 1 John Smith 2013-05-12 13:40:36 UTC
Updated the 'url' to point to the browseable html code coverage report.

Comment 2 John Smith 2013-05-24 19:17:38 UTC
Updated the 'url'

Comment 3 Amar Tumballi 2013-05-28 06:12:48 UTC
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.

Comment 4 Vijay Bellur 2013-05-28 12:14:36 UTC
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.

Comment 5 Justin Clift 2013-05-29 00:54:10 UTC
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?