| Summary: | /bin/mount: double free or corruption (glibc detected) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | John Reiser <jreiser> | ||||
| Component: | util-linux-ng | Assignee: | Karel Zak <kzak> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 15 | CC: | kzak | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | Type: | --- | |||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
The same problem happens when booting directly from physical CD or DVD. I'm not able to reproduce this problem with iso from http://serverbeach1.fedoraproject.org/pub/alt/stage/15-Beta.TC1/Live/i686/Fedora-15-Beta-i686-Live-Desktop.iso in KVM virtual machine. Are you able to reproduce the problem from command line? For example: # mount -t tmpfs tmpfs /media It would be nice to have core dump from the command. # echo 1 > /proc/sys/fs/suid_dumpable # export MALLOC_CHECK_=3 # ulimit -c 10000000 # <the mount command> I verified that my .iso is a correct copy of the one named in Comment #2. The original error occurs during boot before any terminal is available. Today from a text terminal (VT2) command line "mount -t tmpfs tmpfs /media" works. Today I cannot reproduce the original error "*** glibc detected *** /bin/mount: double free or corruption", despite trying on three machines with differing hardware. However, in /var/log/messages I still see the even-earlier complaint: Apr 2 15:56:11 localhost kernel: [ 15.323529] systemd[1]: media.mount mount process exited, code=killed status=6 on all systems. According to the manual page "man 8 mount", the exit status from /sbin/mount is an OR of codes; for '6' the bits are: 2 system error (out of memory, cannot fork, no more loop devices) 4 internal mount bug The three machines all have at least 1GB of RAM and plenty of swapspace, and this is during boot, so there are no human interactions yet. Please, try to reproduce the problem with mount from Fedora-16 or Fedora-17. This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping |
Created attachment 489599 [details] /var/log/messages with glibc diagnostic, traceback, mmaps Description of problem: Running Fedora-15-Beta-i686-Live-Desktop.iso (converted to USB flash storage by "livecd-iso-to-disk Fedora-15-Beta-i686-Live-Desktop.iso /dev/sdc1") gets a glibc-detected double free or corruption during boot. Version-Release number of selected component (if applicable): util-linux-ng-2.18-4.8.fc14.x86_64 How reproducible: every time Steps to Reproduce: 1. boot USB flash memory version of Fedora-15-Beta-i686-Live-Desktop.iso 2. 3. Actual results: mount[390]: *** glibc detected *** /bin/mount: double free or corruption (out): 0x20e11978 *** (see attached /var/log/messages for traceback etc.) Expected results: no problem Additional info: