On Fri, Aug 09, 2013 at 02:14:17PM +0800, dyoung(a)redhat.com wrote:
Chaowang measured the selinux load_policy memory usage, it need ~50M
It's too much under kdump 2nd kernel, it cause more OOM then before.
Since we will relabel the vmcore dir after reboot so let's remove
the selinux dracut module dependency to avoid load_policy in 2nd kernel.
If in the future load_policy memory usage shrinks to an acceptable level
or there's a better solution we can add selinux load_policy back later.
Dave,
I would also like to include description which explains why filesystem
relabeling is not a concern. I am sure this question will comeback later
and I want to record this description in changelog.
Thanks
Vivek
Signed-off-by: Dave Young <dyoung(a)redhat.com>
---
dracut-module-setup.sh | 4 ----
1 file changed, 4 deletions(-)
--- kexec-tools.orig/dracut-module-setup.sh
+++ kexec-tools/dracut-module-setup.sh
@@ -15,10 +15,6 @@ check() {
depends() {
local _dep="base shutdown"
- if sestatus 2>/dev/null | grep -q "SELinux status.*enabled"; then
- _dep="$_dep selinux"
- fi
-
if [ -d /sys/module/drm/drivers ]; then
_dep="$_dep drm"
fi