On Tue, Dec 23, 2008 at 12:00, Derek M Jones <derek@xxxxxxxxxxxx> wrote: > Alexey, > >>> In the Linux kernel, we've got lots of void * address arithmetics: >>> linux/linux-2.6$ make -j 8 CC='gcc -Wpointer-arith' 2>&1 | grep >>> 'warning: pointer of type \'void \*\' used in arithmetic' | uniq | wc >>> -l >>> 45095 >> >> I screwed up, it should be | sort -u | uniq | wc -l >> But it's still 14488. > > This is a sufficiently large number that we ought to consider adding > checks for the usage, for instance: > > 1) Are the arguments really chars of one sort or another and > therefore the parameter ought to be declared as such? You mean, if address arithmetics is performed on a void * cast result, check that the casted type too has sizeof 1? > 2) The arguments have various structure and/or array types and > the storage is being walked over in the called function. Can the > minimum size ever passed be worked out and this information used in > the size_void (my proposed name for a pointer that has either sizeof, > ++ or -- performed on it) function to check for overruns. This won't be possible without dataflow analysis, and sparse currently can't do any. This may change in the future, but if so, we will be able to check for many types of overruns, not only void *. > > 3) Are there any restrictions on passing a void pointer to a > size_void function or vice versa? I cannot think of any obvious > ones, but then I don't know the various kinds of circumstances > in which this happens. > > 4) Other possible fault issues, people? -- To unsubscribe from this list: send the line "unsubscribe linux-sparse" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
