== Comment: #0 - SRIKAR DRONAMRAJU <srikar.dronamraju.com> - 2014-02-21 11:37:35 == When a normal user runs "sudo <some command> " on a fedora 20 ppc64 machine, it crashes $ sudo ls Segmentation fault $ However it works if used as a normal user further we see messages like this on dmesg [ 4580.100414] sudo[32998]: unhandled signal 11 at 0000000000000000 nip 0000000000000000 lr 00003fff96c18570 code 30001 This problem affects su command also. == Comment: #2 - SRIKAR DRONAMRAJU <srikar.dronamraju.com> - 2014-02-25 05:08:30 == (In reply to comment #1) > Is it possible to get the backtrace ? Even with ulimits set properly, sudo doesnt seem to dump core. All other processes were able to dump Starting program: /usr/bin/sudo [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". sudo: effective uid is not 0, is /usr/bin/sudo on a file system with the 'nosuid' option set or an NFS file system without root privileges? [Inferior 1 (process 28091) exited with code 01] Missing separate debuginfos, use: debuginfo-install libselinux-2.2.1-6.fc20.ppc64 pcre-8.33-2.fc20.1.ppc64p7 xz-libs-5.1.2-6alpha.fc20.ppc64p7 The only backtrace I could get is 0xc00000000009b440 : do_exit+0x0/0xb50 [kernel] 0xc00000000009c05c : do_group_exit+0x5c/0x100 [kernel] 0xc0000000000b0f80 : get_signal_to_deliver+0x210/0x720 [kernel] 0xc000000000016b2c : do_signal+0x5c/0x320 [kernel] 0xc000000000016fac : do_notify_resume+0xac/0xc0 [kernel] 0x0 (inexact) I couldnt get the user backtrace though. == Comment: #5 - Kamalesh Babulal <kamaleshb.com> - 2014-10-16 05:11:57 == getenforce and findmnt output
Created attachment 947533 [details] findmnt output default comment by bridge
This error also shows up on RHEL 7, which based on Fedora 19. If LD_LIBRARY_PATH is defined, sudo coredumps for normal user.
Please ignore comment 3. Same defect has been filed in bug 1077389 for RHEL 7.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is 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 change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.