Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1263974 - Second [heap] mapping is shown as "anonymous" (no pathname field) with PIE binary [NEEDINFO]
Summary: Second [heap] mapping is shown as "anonymous" (no pathname field) with PIE bi...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 24
Hardware: i386
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-09-17 08:41 UTC by Pavel Raiskup
Modified: 2017-04-28 17:23 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-04-28 17:23:12 UTC
Type: Bug
Embargoed:
jforbes: needinfo?

Attachments (Terms of Use)
Reproducer (1.03 KB, application/x-gzip)
2015-10-21 04:19 UTC, Pavel Raiskup 		no flags Details
View All

Description Pavel Raiskup 2015-09-17 08:41:19 UTC 
Tested on i386 with simple program doing shm_open()/mmap() and malloc() with
smaller chunks than M_MMAP_THRESHOLD, by
'MALLOC_MMAP_THRESHOLD_=524288 ./program'.  I've got something like:

$ cat /proc/$PROCPID/maps
...
728e6000-738e6000 rw-p 00000000 00:00 0 
738e6000-79ce6000 rw-s 00000000 00:13 93153      /dev/shm/testing-shm-mapping-9
79ce6000-800e6000 rw-s 00000000 00:13 93152      /dev/shm/testing-shm-mapping-8
800e6000-800e7000 r-xp 00000000 fd:01 50501118   /home/praiskup/shmget/program
800e7000-800e8000 r--p 00000000 fd:01 50501118   /home/praiskup/shmget/program
800e8000-800e9000 rw-p 00001000 fd:01 50501118   /home/praiskup/shmget/program
800f2000-854f3000 rw-p 00000000 00:00 0          [heap]
85543000-8b943000 rw-s 00000000 00:13 93150      /dev/shm/testing-shm-mapping-7
8b943000-91d43000 rw-s 00000000 00:13 93149      /dev/shm/testing-shm-mapping-6
91d43000-98143000 rw-s 00000000 00:13 93147      /dev/shm/testing-shm-mapping-5
98143000-9e543000 rw-s 00000000 00:13 93146      /dev/shm/testing-shm-mapping-4
9e543000-a4943000 rw-s 00000000 00:13 93145      /dev/shm/testing-shm-mapping-3
a4943000-aad43000 rw-s 00000000 00:13 93142      /dev/shm/testing-shm-mapping-2
aad43000-b1143000 rw-s 00000000 00:13 93140      /dev/shm/testing-shm-mapping-1
b1143000-b7543000 rw-s 00000000 00:13 93139      /dev/shm/testing-shm-mapping-0
b7543000-b7545000 rw-p 00000000 00:00 0 
b7545000-b755d000 r-xp 00000000 fd:01 51660062   /usr/lib/libpthread-2.21.so
b755d000-b755f000 r--p 00017000 fd:01 51660062   /usr/lib/libpthread-2.21.so
...

Note that the first map '728e6000-738e6000' is getting bigger with more
malloc() requests.  But it is not marked as [heap] the same way it is done for
'800f2000-854f3000' mapping.
Comment 1 Pavel Raiskup 2015-09-17 08:43:06 UTC 
This might be not strictly related to PIE or i386, but I haven't done more
testing than that.  The only thing: I'm curious about the missing [heap]
stamp.
Comment 2 Justin M. Forbes 2015-10-20 19:26:58 UTC 
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 22 kernel bugs.

Fedora 22 has now been rebased to 4.2.3-200.fc22.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 23, and are still experiencing this issue, please change the version to Fedora 23.

If you experience different issues, please open a new bug report for those.
Comment 3 Pavel Raiskup 2015-10-21 04:19:00 UTC 
Created attachment 1084963 [details]
Reproducer

I forgot to attach the reproducers, sorry.

Still reproducible on my F23 x86_64 box:
  $ make && MALLOC_MMAP_THRESHOLD_=524288 ./program 15 5000
  using 15 maps and 5000 mallocs
  My PID is 14182
  00048000-08048000 rw-p 00000000 00:00 0
  ^^^ Missing [heap] stamp

  08048000-08049000 r-xp 00000000 fd:02 2280118  /tmp/program
  08049000-0804a000 r--p 00000000 fd:02 2280118  /tmp/program
Comment 4 Laura Abbott 2016-09-23 19:34:50 UTC 
*********** MASS BUG UPDATE **************
 
We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 23 kernel bugs.
 
Fedora 23 has now been rebased to 4.7.4-100.fc23.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.
 
If you have moved on to Fedora 24 or 25, and are still experiencing this issue, please change the version to Fedora 24 or 25.
 
If you experience different issues, please open a new bug report for those.
Comment 5 Pavel Raiskup 2016-09-26 10:25:35 UTC 
https://github.com/praiskup/bug-reports/commit/0cfa8a8e8ebf1d73f8a7ea7faf9421771a0981dd
Comment 6 Justin M. Forbes 2017-04-11 14:48:20 UTC 
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There are a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 24 kernel bugs.

Fedora 25 has now been rebased to 4.10.9-100.fc24.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 26, and are still experiencing this issue, please change the version to Fedora 26.

If you experience different issues, please open a new bug report for those.
Comment 7 Justin M. Forbes 2017-04-28 17:23:12 UTC 
*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 weeks. If you are still experiencing this issue, please reopen and attach the 
relevant data from the latest kernel you are running and any data that might have been requested previously.
Note You need to log in before you can comment on or make changes to this bug.