On Sun, Nov 06, 2016 at 09:49:38AM +0100, Luc Van Oostenryck wrote: > On Sat, Nov 05, 2016 at 08:30:31AM +0800, Christopher Li wrote: > > Those function originally all assume the list > > are packed. > > > > Is there usage case in current sparse that > > feed unpacked list to those function? > > > > Chris OK, I've checked this on a more substantial amount of code than the testsuite: the kernel for x86-64 with allyesconfig and I confirm that there is not a single out-of-bounds access to any ->list[], wich is what matters. Nevertheless, there are two cases (in cse.c and evaluate.c) where elements are deleted from a list which is not directly repacked at the end of the loop and it's not obvious in the code why it's OK to not repack them. Luc -- 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
