> We could, for example, wrap things like userspace pointers, __be numbers, > ioport addresses and control access to them that way, but I don't know that it > gains a whole load that sparse doesn't give us.
The problem with sparse is that it is not mandatory part of a build process. And it spams lot ATM.
