From: Kees Cook > Sent: 17 June 2021 05:27 > > In preparation for FORTIFY_SOURCE performing compile-time and run-time > field bounds checking for memcpy(), memmove(), and memset(), avoid > intentionally writing across neighboring array fields. > > Give memcpy() a specific source pointer type so it can correctly > calculate the bounds of the copy. Doesn't the necessity of this sort of patch just sidestep the run-time checking and really indicate that it is just a complete waste of cpu resources? I bet code changes to avoid/fix the reported errors will introduce more bugs than the test itself will really find. David - Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK Registration No: 1397386 (Wales)
