Description of problem: An update of selinux-policy-targeted results in the following: Updating : selinux-policy-targeted-3.11.0-8.fc18.noarch 1086/2414 /var/tmp/rpm-tmp.a2JFud: line 10: 10005 Segmentation fault (core dumped) /usr/sbin/semodule -n -s targeted -r xfs kudzu kerneloops execmem openoffice ada tzdata hal hotplug howl java mono moilscanner gamin audio_entropy audioentropy iscsid polkit_auth polkit rtkit_daemon ModemManager telepathysofiasip ethereal passanger qpidd pyzor razor 2> /dev/null /var/tmp/rpm-tmp.a2JFud: line 10: 10014 Segmentation fault (core dumped) /usr/sbin/semodule -B -n -s targeted That indeed resulted in dumping two cores in /, each 314M in size. gdb reports "Program terminated with signal 11, Segmentation fault". abrtd did not catch anything Version-Release number of selected component (if applicable): selinux-policy-targeted-3.11.0-8.fc18.noarch How reproducible: Running '/usr/sbin/semodule -B -n -s targeted' appears to result in segfaults. Additional info: Selinux is actually disabled on a test system. That seems to be different than bug 810413.
I believe this is fixed in the current toolchain.