On Mon, 29 Apr 2024, Kees Cook wrote: > this isn't a case where we can show identical binary output, since this > actively adds overflow checking via kcalloc() internals. > > ... > > it is a trivially correct change that uses a more robust API and more > idiomatic allocation sizeof()s If a change is "trivially correct" then the proof is trivial too. Based only on what you wrote above, omitting the overflow check would give binary equivalence. That validates the driver change (for hardware you lack). But, since a build without the overflow check must contain a second change, you must validate that change too by showing that kcalloc() internals still work for every other caller. (You do this using hardware you have.)
