On Fri, Dec 13, 2024 at 09:13:54PM -0800, Jared Finder wrote:
> On 2024-12-03 06:07, Günther Noack wrote:
> > On Tue, Dec 03, 2024 at 02:53:27PM +0100, Günther Noack wrote:
> > > Hanno, you are the original author of this patch and you have done a
> > > more
> > > detailed analysis on the TIOCLINUX
On 2024-12-03 06:07, Günther Noack wrote:
On Tue, Dec 03, 2024 at 02:53:27PM +0100, Günther Noack wrote:
Hanno, you are the original author of this patch and you have done a
more
detailed analysis on the TIOCLINUX problems than me -- do you agree
that this
weakened check would still be sufficie
GCC performs value range tracking for variables as a way to provide better
diagnostics. One place this is regularly seen is with warnings associated
with bounds-checking, e.g. -Wstringop-overflow, -Wstringop-overread,
-Warray-bounds, etc. In order to keep the signal-to-noise ratio high,
warnings ar
Sorry for the delay in my reply -- I've been trying to catch up on stuff
after 2 weeks off.
On Tue, Dec 03, 2024 at 02:13:45PM +, Lorenzo Stoakes wrote:
> On Wed, Aug 14, 2024 at 09:59:47AM -0700, Kees Cook wrote:
> > On Tue, 06 Aug 2024 21:49:26 +, jef...@chromium.org wrote:
> > > From: J
On Fri, Dec 13, 2024 at 02:49:20PM +0530, Nilay Shroff wrote:
> ./include/linux/fortify-string.h:620:63: error: void value not ignored as it
> ought to be
Whoops! Thanks, I had only spot-checked padata.o :( I will fix this up
and send a v2.
--
Kees Cook
On 12/13/24 07:39, Kees Cook wrote:
> GCC performs value range tracking for variables as a way to provide better
> diagnostics. One place this is regularly seen is with warnings associated
> with bounds-checking, e.g. -Wstringop-overflow, -Wstringop-overread,
> -Warray-bounds, etc. In order to k
