https://github.com/google/sanitizers/issues/1716#issuecomment-2010399341
Summarizing: newer ThreadSanitizer has been updated to be able to work
with vm.mmap_rnd_bits = 30, but not higher than that. For other cases,
it will now re-execute the binary with ASLR disabled, if possible.
For most
It's indeed the bump of vm.mmap_rnd_bits from 28 to 32, which is part of
the changelog in https://launchpad.net/ubuntu/+source/linux/6.5.0-25.25
:
* test_021_aslr_dapper_libs from ubuntu_qrt_kernel_security failed on K-5.19 /
J-OEM-6.1 / J-6.2 AMD64 (LP: #1983357)
- [Config]: set
This could be the same thing reported in
https://github.com/google/sanitizers/issues/1716 ("Thread Sanitizer
FATAL error on kernel version 6.6.6-x").
** Bug watch added: github.com/google/sanitizers/issues #1716
https://github.com/google/sanitizers/issues/1716
--
You received this bug
One other note, I only get the "unexpected memory mapping" error on
amd64. On arm64 machines with 6.5.0-25.25~22.04.1, ThreadSanitizer works
without issues.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu.
Public bug reported:
We updated a number of (amd64) machines from linux-
image-6.5.0-21-generic (6.5.0-21.21~22.04.1) to linux-
image-6.5.0-25-generic (6.5.0-25.25~22.04.1), and this caused
ThreadSanitizer-instrumented programs to immediately exit with an error
similar to:
FATAL:
Note that similar to the older gcc and upstream sanitizer bugs, this
problem may be caused by some kernel API now returning a slightly
different result, so it could be debatable whether the issue should be
fixed in ThreadSanitizer, or in the kernel itself.
--
You received this bug notification
6 matches
Mail list logo
