New submission from Alexey Izbyshev <izbys...@ispras.ru>:
address_in_range() in Objects/obmalloc.c may access memory that is mapped but
is considered free by the underlying libc allocator. In #18596, address
sanitizing was disabled for this function. But thread and memory sanitizers
similarly trip on this function:
WARNING: ThreadSanitizer: heap-use-after-free (pid=24361)
Read of size 4 at 0x7b7c00000020 by main thread:
#0 address_in_range /scratch2/izbyshev/cpython/Objects/obmalloc.c:1312:23
(python+0x59e912)
==3515==WARNING: MemorySanitizer: use-of-uninitialized-value
#0 0x9713f8 in address_in_range
/scratch2/izbyshev/cpython/Objects/obmalloc.c:1313:35
I suggest to disable them for this function as well.
----------
components: Interpreter Core
messages: 329561
nosy: benjamin.peterson, izbyshev, serhiy.storchaka, vstinner
priority: normal
severity: normal
status: open
title: Disable thread and memory sanitizers for address_in_range()
type: enhancement
versions: Python 2.7, Python 3.6, Python 3.7, Python 3.8
_______________________________________
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue35204>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
