Bug 196537 - [regression] since commit eab09532d400 AddressSanitizer shadow memory range interleaves with existing memory mapping
Summary: [regression] since commit eab09532d400 AddressSanitizer shadow memory range i...
Status: NEW
Alias: None
Product: Other
Classification: Unclassified
Component: Other (show other bugs)
Hardware: Intel Linux
: P1 normal
Assignee: other_other
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-07-30 14:00 UTC by Max Bruckner
Modified: 2017-08-07 09:29 UTC (History)
4 users (show)

See Also:
Kernel Version: 4.12.3
Subsystem:
Regression: Yes
Bisected commit-id:

Attachments
AddressSanitizer error message (2.58 KB, text/plain)
2017-07-30 14:00 UTC, Max Bruckner 		Details
Log of git bisect (2.94 KB, text/plain)
2017-07-30 14:01 UTC, Max Bruckner 		Details
cpuinfo (3.76 KB, text/plain)
2017-07-30 14:01 UTC, Max Bruckner 		Details
Add an attachment (proposed patch, testcase, etc.)

Description Max Bruckner 2017-07-30 14:00:14 UTC 
Created attachment 257763 [details]
AddressSanitizer error message

When upgrading from 4.11 to 4.12.3 suddenly AddressSanitizer stopped working. Tested with a simple hello world and compiling with clang and `-fsanitize=address`. Clang version 4.0.1.

Binaries produced that way stop to work with an error message complaining that the shadow memory range interleaves with an existing memory mapping.

After some investigation I started bisecting the issue and found the following commit to be the culprit:

eab09532d400 binfmt_elf: use ELF_ET_DYN_BASE only for PI

I'm on Intel x86_64, cpuinfo in the attachment. I didn't try on different hardware, it didn't happen in VirtualBox though but happened in QEMU + KVM.
Comment 1 Max Bruckner 2017-07-30 14:01:03 UTC 
Created attachment 257765 [details]
Log of git bisect
Comment 2 Max Bruckner 2017-07-30 14:01:33 UTC 
Created attachment 257767 [details]
cpuinfo
Comment 3 Max Bruckner 2017-07-30 14:02:39 UTC 
Note: The offending commit has been added in 4.12.3
Comment 4 Max Bruckner 2017-08-01 20:19:53 UTC 
Issue on the AddressSanitizer GitHub issue tracker: https://github.com/google/sanitizers/issues/837
Note You need to log in before you can comment on or make changes to this bug.