Sparse
{{Short description|Computer software coding tool}}
{{about|a software static analysis tool}}
{{Infobox software
| name = Sparse
| author = Linus Torvalds
| developer = Josh Triplett, Christopher Li, Luc Van Oostenryck
| released = 2003
| latest release version = 0.6.4
| latest release date = {{Start date and age|2021|09|06}}{{cite mailing list
| title = Sparse 0.6.4
| author = Luc Van Oostenryck
| date = 2021-09-06
| mailing-list = linux-sparse@vger.kernel.org
| url = https://lore.kernel.org/all/0bd4f497-05f8-5636-5548-d8b289ea0dc0@codethink.co.uk/T/
| accessdate = 2024-05-08
}}
| programming language = C
| operating system = Linux, BSD, macOS, MinGW, Cygwin
| genre = Static code analysis
| license = MIT License
| website = {{URL|sparse.docs.kernel.org}}
}}
Sparse is a computer software tool designed to find possible coding faults in the Linux kernel.{{cite conference
| title = Semantic patches for documenting and automating collateral evolutions in Linux device drivers
| author1=Yoann Padioleau |author2=René Rydhof Hansen |author3=Julia L. Lawall|author3-link= Julia Lawall |author4=Gilles Muller | year= 2006
| conference = Proceedings of the 3rd workshop on Programming languages and operating systems: linguistic support for modern operating systems
| isbn = 1-59593-577-0
| doi = 10.1145/1215995.1216005
| citeseerx=10.1.1.122.7080 | quote= The Linux community has recently begun using various tools to better analyze C code. Sparse is a library that, like a compiler front end, provides convenient access to the abstract syntax tree and typing information of a C program.
}} Unlike other such tools, this static analysis tool was initially designed to only flag constructs that were likely to be of interest to kernel developers, such as the mixing of pointers to user and kernel address spaces.
Sparse checks for known problems and allows the developer to include annotations in the code that convey information about data types, such as the address space that pointers point to and the locks that a function acquires or releases.
Linus Torvalds started writing Sparse in 2003. Josh Triplett was its maintainer from 2006, a role taken over by Christopher Li in 2009{{cite mailing list
| title = Sparse 0.4.2 released
| author = Christopher Li
| date = 2009-10-16
| mailing-list = linux-sparse
| url = http://marc.info/?l=linux-sparse&m=125570805231414&w=2
| accessdate = 2010-11-06
}}
and by Luc Van Oostenryck in November 2018.{{Citation
| url = https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/MAINTAINERS?id=4e962ff6e34f44c400c548da0c1e2393053a691e
| title = change Sparse's maintainer
| accessdate = December 10, 2018
| ref = none
}}
Sparse is released under the MIT License.
Annotations
Some of the checks performed by Sparse require annotating the source code using the __attribute__
GCC extension, or the Sparse-specific __context__
specifier.{{cite web
| url = https://gcc.gnu.org/onlinedocs/gcc/Attribute-Syntax.html
| title = Attribute Syntax — Using the GNU Compiler Collection (GCC)
| publisher = Free Software Foundation
| accessdate = 2010-11-13
}} Sparse defines the following list of attributes:
address_space(num)
bitwise
force
context(expression,in_context,out_context)
When an API is defined with a macro, the specifier __attribute__((context(...)))
can be replaced by __context__(...)
.
=Linux kernel definitions=
The Linux kernel defines the following short forms as pre-processor macros in files [http://lxr.linux.no/linux+*/include/linux/compiler.h linux/compiler.h] and [http://lxr.linux.no/linux+*/include/linux/types.h linux/types.h] (when building without the __CHECKER__
flag, all these annotations are removed from the code):
- ifdef __CHECKER__
- define __user __attribute__((noderef, address_space(1)))
- define __kernel __attribute__((address_space(0)))
- define __safe __attribute__((safe))
- define __force __attribute__((force))
- define __nocast __attribute__((nocast))
- define __iomem __attribute__((noderef, address_space(2)))
- define __must_hold(x) __attribute__((context(x,1,1)))
- define __acquires(x) __attribute__((context(x,0,1)))
- define __releases(x) __attribute__((context(x,1,0)))
- define __acquire(x) __context__(x,1)
- define __release(x) __context__(x,-1)
- define __cond_lock(x,c) ((c) ? ({ __acquire(x); 1; }) : 0)
- define __percpu __attribute__((noderef, address_space(3)))
- ifdef CONFIG_SPARSE_RCU_POINTER
- define __rcu __attribute__((noderef, address_space(4)))
- else
- define __rcu
- endif
extern void __chk_user_ptr(const volatile void __user *);
extern void __chk_io_ptr(const volatile void __iomem *);
- else
- define __user
- define __kernel
- define __safe
- define __force
- define __nocast
- define __iomem
- define __chk_user_ptr(x) (void)0
- define __chk_io_ptr(x) (void)0
- define __builtin_warning(x, y...) (1)
- define __must_hold(x)
- define __acquires(x)
- define __releases(x)
- define __acquire(x) (void)0
- define __release(x) (void)0
- define __cond_lock(x,c) (c)
- define __percpu
- define __rcu
- endif
- ifdef __CHECKER__
- define __bitwise __attribute__((bitwise))
- else
- define __bitwise
- endif
=Examples=
The types __le32
and __be32
represent 32-bit integer types with different endianness. However, the C language does not allow to specify that variables of these types should not be mixed. The bitwise
attribute is used to mark these types as restricted, so Sparse will give a warning if variables of these types or other integer variables are mixed:
typedef __u32 __bitwise __le32;
typedef __u32 __bitwise __be32;
To mark valid conversions between restricted types, a casting with the force
attribute is used to avoid Sparse giving a warning.
See also
{{Portal|Free and open-source software}}
References
{{reflist}}
Further reading
- {{cite web
| title = Sparse: a look under the hood
| author = Neil Brown
| date = 2016-06-08
| work = LWN.net
| url = https://lwn.net/Articles/689907/
| accessdate = 2021-11-26
}}
- {{cite web
| title = Finding kernel problems automatically
| author = Jonathan Corbet
| date = 2004-06-01
| work = LWN.net
| url = https://lwn.net/Articles/87538/
| accessdate = 2021-11-26
}}
- {{cite web
| title = Linus & the Lunatics, Part I
| author = Doc Searls
| date = 2003-11-24
| work = Linux Journal
| url = http://www.linuxjournal.com/article/7272
| accessdate = 2021-11-26
}}
- {{cite conference
| title = Putting LTP to test—Validating both the Linux kernel and Test-cases
|author1=Subrata Modak |author2=Balbir Singh |author3=Yamato Masatake | year = 2009
| conference = Ottawa Linux Symposium 2009
| conference-url = https://www.kernel.org/doc/ols/2009/
| pages = 209–220
| url = https://www.kernel.org/doc/ols/2009/ols2009-pages-209-220.pdf
| accessdate = 2021-11-26
}}
- {{cite thesis
| degree = M.Sc.
| title = Detection of Static Flaws in Changesets
| author = Daniel De Graaf
| year = 2010
| publisher = Iowa State University
| location = Ames, Iowa
| accessdate = 2010-11-07
| url = http://archives.ece.iastate.edu/archive/00000566/01/thesis.pdf
| oclc = 665146513
}}
External links
- [https://sparse.docs.kernel.org Official documentation]
- [https://www.kernel.org/doc/html/latest/dev-tools/sparse.html Using sparse for typechecking], Linux Kernel Documentation
- {{man|1|sparse|Linux|Semantic Parser for C}}
- {{man|1|cgcc|Linux|Compiler wrapper to run Sparse after compiling}}
Category:Static program analysis tools