Details
-
Technical task
-
Resolution: Fixed
-
Minor
-
Lustre 2.2.0
-
FC13 running clang-analyzer-2.8-10.fc13.x86_64
-
4812
Description
Tracking bug for warnings produced by the clang-analyzer static code analysis tool.
The first one is a trivial printk() format warning due to the use of "%Lu" for LPU64, and other places in the code. The "%L" format specifier is a GCCism that is deprecated in favor of "%ll" from C99.
Attachments
Issue Links
- is related to
-
LU-2675 clang: code cleanups for sparse static analyzer
-
- Resolved
-
- Trackbacks
-
Changelog 2.2 version 2.2.0 Support for networks: o2iblnd OFED 1.5.4 Server support for kernels: 2.6.32220.4.2.el6 (RHEL6) Client support for unpatched kernels: 2.6.18274.18.1.el5 (RHEL5) 2.6.32220.4.2.el6 (RHEL6) 2.6.32.360....
-
Project Ideas Information for Developers Working on Lustre will quickly introduce a developer to the always interesting and impressive world of HPC, where the systems are the largest in the world,...
FWIW I've compiled Lustre 2.1.54 patchless client on CentOS 6.2 with Clang's static analyzer (LLVM 3.0).
I decided to disable the static analyzer check "core.NullDereference" because it detects lots of bugs (521). However, based on a first short glance most of them are dubious because the analyzer seems to get confused by Lustre's LASSERT(). (And including all of these 521 bugs would make the tarball larger than the Jira upload file limit.)
Here's the bug summary:
Check out the annotated source in the attached tarball with a web browser.
This is how the source was compiled:
touch META
sh autogen.sh
scan-build ./configure --disable-server \
--with-linux=/usr/src/kernels/2.6.32-220.2.1.el6.x86_64 \
--with-linux-obj=/lib/modules/2.6.32-220.2.1.el6.x86_64/build/ \
--with-downstream-release=wc1
mkdir ./lustre-2.1.54-scan-build
scan-build -o ./lustre-2.1.54-scan-build/ \
-disable-checker core.NullDereference \
make -j 24