Hide Forgot
Description of problem: * sediff gets killed by OOM killer when --allow or --dontaudit or --stats parameter is used Version-Release number of selected component (if applicable): setools-console-3.3.8-1.el7.x86_64 How reproducible: always Steps to Reproduce: # sediff --allow /etc/selinux/targeted/policy/policy.29 \; /etc/selinux/targeted/policy/policy.30 Killed # echo $? 137 # dmesg | tail -n 2 [ 4033.789560] Out of memory: Kill process 5430 (sediff) score 672 or sacrifice child [ 4033.789561] Killed process 5430 (sediff) total-vm:1360016kB, anon-rss:569884kB, file-rss:0kB # Actual results: * sediff is killed by OOM killer because it consumed too much memory Expected results: * sediff works as expected and terminates correctly
sediff finished on a ppc64 machine equipped by 16GB RAM. The peak of memory allocated by the sediff process in about 7GB.
I'm not sure we can do it for RHEL-7.3. It would need an upstream patch while setools3 is considered mature and should be obsoleted soon by setools4. As a workaround, if you need to do memory demanding operations, just raise amount of memory attached to your VMs.