Re: HARDMEMTESTS: apparent stale stack pointer written to L->top by checkGC (heap OOB read in traversethread)

> I would like to report a problem I ran into while testing the current 
> master (7579fc9d7ed90240487251dfb69168f8e64e9294) built with 
> -DHARDMEMTESTS: AddressSanitizer reports a heap out-of-bounds read in 
> traversethread. From my reading of the code, it looks as if checkGC(L, ra + 
> 1) wrote a stale stack pointer to L->top after the GC step moved the stack, 
> but I may well be missing something about the intended invariants here, so 
> I would appreciate your view. I found it while fuzzing with an 
> OSS-Fuzz-style harness, but it also reproduces with the plain interpreter.

Thanks for the report. Indeed, the macro 'luaC_condGC' should not
repeat 'pre' and 'pos' with HARDMEMTESTS.

-- Roberto

-- 
You received this message because you are subscribed to the Google Groups "lua-l" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To view this discussion visit https://groups.google.com/d/msgid/lua-l/20260820201453.GA104854%40arraial.inf.puc-rio.br.