On Wed, 2011-08-31 at 17:52 +0200, Yves-Alexis Perez wrote: > Package: linux-2.6 > Version: 3.0.0-3 > Severity: wishlist > > Hey, > > this was already asked as part of #605090 but I had the impression that > opening a bug was needed since people were aware, but I was wrong. > > So here's a wishlist bug. Could DEBUG_STRICT_USER_COPY_CHECKS be > enabled? > > It's used to enforce checks for the various copy_* to prevent overflows > etc. This is done at compile time, and, afaict, it worked fine (on > i386/amd64 Debian kernels) since 2.6.37.
As I wrote on #605090: Without the strict check, the crap code produces a compile-time warning and a run-time warning and *no copying*. With the strict check, the crap code results in FTBFS (but only on i386 and s390!). So how is this an improvement for us? Ben.
signature.asc
Description: This is a digitally signed message part
