On Sun, Dec 09, 2018 at 11:25:57PM +0100, Luc Van Oostenryck wrote: > On Sun, Dec 09, 2018 at 11:17:50PM +0100, Luc Van Oostenryck wrote: > > On Sun, Dec 09, 2018 at 02:53:09PM -0700, Tycho Andersen wrote: > > > > * add a new annotation to force sparse to check the byte count > > > > (I'm thinking about __range__/OP_RANGE or something similar). > > > > > > Yes, I was playing around with inventing some check like this without > > > the need for an annotation. It's not clear to me if it's going to work > > > or not yet, though :). Top two patches here are what I was playing > > > with: > > > > > > https://github.com/tych0/sparse/commits/check-as-infoleaks > > > > > > Then src is not a PSEUDO_SYM (it should be a PSEUDO_REG equal to > > a PSEUDO_SYM plus fred's offset). > > There is the same problem for the first patch/check_no_kernel_pointers(). > But the case PSEUDO_SYM + offset should be easy to handle. Right thanks. Unfortunately in the two cases I know about where this could catch something: [1]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/block/floppy.c?h=v4.20-rc2&id=65eea8edc315589d6c993cf12dbb5d0e9ef1fe4e [2]: https://lkml.org/lkml/2018/11/3/142 there is some void* casting polluting the arguments, so I don't think it will work. Do you have any tricks for things like this? Thanks! Tycho
