RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1312850 - Address sanitized binary crashed on ppc64 with CHECK failed: ((AddrIsInMem(stack_bottom_))) != (0)
Summary: Address sanitized binary crashed on ppc64 with CHECK failed: ((AddrIsInMem(st...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gcc
Version: 7.2
Hardware: ppc64
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Jakub Jelinek
QA Contact: Michael Petlan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-29 11:49 UTC by Miloš Prchlík
Modified: 2016-11-04 06:27 UTC (History)
6 users (show)

Fixed In Version: gcc-4.8.5-6.el7
Doc Type: No Doc Update
Doc Text:
undefined
Clone Of:
Environment:
Last Closed: 2016-11-04 06:27:58 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2433 0 normal SHIPPED_LIVE gcc bug fix and enhancement update 2016-11-03 14:01:11 UTC

Description Miloš Prchlík 2016-02-29 11:49:50 UTC 
Description of problem:

[root@ibm-p8-01-lp4 ~]# cat t.c
int main(int argc, char **argv) {  return 0; }
[root@ibm-p8-01-lp4 ~]# gcc -o t -fsanitize=address  t.c
[root@ibm-p8-01-lp4 ~]# ASAN_OPTIONS=verbosity=1 ./t
==28721== Parsed ASAN_OPTIONS: verbosity=1
==28721== AddressSanitizer: libc interceptors initialized
|| `[0x040000000000, 0x0fffffffffff]` || HighMem    ||
|| `[0x028000000000, 0x03ffffffffff]` || HighShadow ||
|| `[0x024000000000, 0x027fffffffff]` || ShadowGap  ||
|| `[0x020000000000, 0x023fffffffff]` || LowShadow  ||
|| `[0x000000000000, 0x01ffffffffff]` || LowMem     ||
MemToShadow(shadow): 0x024000000000 0x0247ffffffff 0x025000000000 0x027fffffffff
red_zone=16
malloc_context_size=30
SHADOW_SCALE: 3
SHADOW_GRANULARITY: 8
SHADOW_OFFSET: 20000000000
==28721== Installed the sigaction for signal 11
==28721== AddressSanitizer CHECK failed: ../../../../libsanitizer/asan/asan_thread.cc:74 "((AddrIsInMem(stack_bottom_))) != (0)" (0x0, 0x0)
=================================================================
==28721== ERROR: AddressSanitizer: unknown-crash on address 0x3fffe93b49b0 at pc 0x3fffa875994c bp 0x3fffe93b34f0 sp 0x3fffe93b3560
WRITE of size 1392 at 0x3fffe93b49b0 thread T0
==28721== AddressSanitizer: while reporting a bug found another one.Ignoring.

Could it possibly be upstream issue https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55975 ?


Version-Release number of selected component (if applicable):

gcc-4.8.5-4.el7.ppc64
libasan-4.8.5-4.el7.ppc64

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 2 Martin Sebor 2016-05-17 02:31:36 UTC 
Let me look into this.
Comment 3 Martin Sebor 2016-05-25 18:25:16 UTC 
The following patch backported from trunk fixes the problem on my powerpc64 server:

--- libsanitizer/asan/asan_rtl.cc.~0~
+++ libsanitizer/asan/asan_rtl.cc
@@ -306,13 +306,15 @@
 #if !ASAN_FIXED_MAPPING
 #if SANITIZER_WORDSIZE == 64
 # if defined(__powerpc64__)
-  // FIXME:
   // On PowerPC64 we have two different address space layouts: 44- and 46-bit.
-  // We somehow need to figure our which one we are using now and choose
+  // We somehow need to figure out which one we are using now and choose
   // one of 0x00000fffffffffffUL and 0x00003fffffffffffUL.
   // Note that with 'ulimit -s unlimited' the stack is moved away from the top
   // of the address space, so simply checking the stack address is not enough.
-  kHighMemEnd = (1ULL << 44) - 1;  // 0x00000fffffffffffUL
+  // This should (does) work for both PowerPC64 Endian modes.
+  // Similarly, aarch64 has multiple address space layouts: 39, 42 and 47-bit.
+  kHighMemEnd
+    = (1ULL << (MostSignificantSetBitIndex(GET_CURRENT_FRAME()) + 1)) - 1;
 # else
   kHighMemEnd = (1ULL << 47) - 1;  // 0x00007fffffffffffUL;
 # endif

The patch adjusts the memory mapping from the one shown in comment #0 to match GCC trunk:

|| `[0x0a0000000000, 0x3fffffffffff]` || HighMem    ||
|| `[0x034000000000, 0x09ffffffffff]` || HighShadow ||
|| `[0x024000000000, 0x033fffffffff]` || ShadowGap  ||
|| `[0x020000000000, 0x023fffffffff]` || LowShadow  ||
|| `[0x000000000000, 0x01ffffffffff]` || LowMem     ||
MemToShadow(shadow): 0x024000000000 0x0247ffffffff 0x026800000000 0x033fffffffff

The patch also makes quite an improvement to the asan test results:

  +-- BASELINE
  |   +-- PATCHED
  |   |
  V   V   TEST
 10       c-c++-common/asan/clone-test-1.c
  8       c-c++-common/asan/global-overflow-1.c
  8       c-c++-common/asan/heap-overflow-1.c
  8       c-c++-common/asan/memcmp-1.c
  8   5   c-c++-common/asan/null-deref-1.c
  1       c-c++-common/asan/rlimit-mmap-test-1.c
  8       c-c++-common/asan/sanity-check-pure-c-1.c
  3       c-c++-common/asan/sleep-before-dying-1.c
  8       c-c++-common/asan/stack-overflow-1.c
  3       c-c++-common/asan/strip-path-prefix-1.c
  8       c-c++-common/asan/strncpy-overflow-1.c
 10  10   c-c++-common/asan/swapcontext-test-1.c
  8       c-c++-common/asan/use-after-free-1.c
  6       g++.dg/asan/deep-stack-uaf-1.C
  8       g++.dg/asan/deep-tail-call-1.C
  8       g++.dg/asan/deep-thread-stack-1.C
  8       g++.dg/asan/default-options-1.C
  8       g++.dg/asan/interception-failure-test-1.C
  8       g++.dg/asan/interception-malloc-test-1.C
  8       g++.dg/asan/interception-test-1.C
  8       g++.dg/asan/large-func-test-1.C
  8       g++.dg/asan/pr55617.C
  3       g++.dg/asan/symbolize-callback-1.C
Comment 5 Jakub Jelinek 2016-05-26 08:07:39 UTC 
Thanks, that is all I need.
Comment 7 Michael Petlan 2016-07-25 10:22:08 UTC 
test fails with gcc-4.8.5-4.el7.ppc64
test passes for gcc-4.8.5-9.el7.ppc64

VERIFIED
Comment 9 errata-xmlrpc 2016-11-04 06:27:58 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-2433.html
Note You need to log in before you can comment on or make changes to this bug.