Hide Forgot
Created attachment 920458 [details] Traceback and Memory map from /var/log/messages Description of problem: If SELinux is disabled, nmtui crashes, when you try to set/change the hostname. Version-Release number of selected component (if applicable): * NetworkManager-0.9.9.1-25.git20140326.4dba720 How reproducible: * Always Steps to Reproduce: 1. Disable SELinux in /etc/sysconfig/selinux 2. Reboot 3. Check with "sestatus", that it's really disabled 4. Run "nmtui" 5. Choose "Set system hostname" 6. Type in a hostname, like "xxx.yyy" and hit OK Actual results: * Application freezes. * NetworkManager process crashes (/var/log/messages): *** Error in `/usr/sbin/NetworkManager': free(): invalid pointer: 0x00007fa24ae35240 *** Expected results: * Hostname should be set and application should return back to prompt. Additional info: * If you re-enable SELinux in /etc/sysconfig/selinux and reboot, setting the hostname in nmtui is possible again. * I discovered this problem in CentOS7, but I think it's a bug directly in RHEL7.
Thanks for the report. I can reproduce the crash on latest RHEL7. The problem is not in nmtui, but in NM ifcfg-rh plugin. When SELinux is disabled SELinux, getfscreatecon() fails and we tried to free uninitialized context later. Testcase: 1) Enable ifcfg-rh plugin in /etc/NetworkManger/NetworkManger.conf plugins=ifcfg-rh 2) Edit /etc/sysconfig/selinux to contain SELINUX=disabled 3) Reboot 4) Set hostname via nmcli, nmtui or D-Bus SaveHostname() call nmcli gen hostname this-is-my-pc 5) NM crashes
Created attachment 920529 [details] [PATCH] Patch fixing the crash This patch fixes the crash in ifcfg-rh.
yeah, looks right
Committed upstream: 93f7fa9 ifcfg-rh: fix a crash on setting hostname with SELinux disabled (rh #1122826)
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-2015-0311.html