Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
It appears that the kernel is having a difficult time allocating kernel memory for the SELinux policy load, I'm guessing this is due to memory pressure caused by the fact that kernel is a kdump recovery kernel and a good portion of the physical memory is reserved for dumping to disk.
Is there any reason why we are loading the SELinux policy in the kdump kernel? This kernel boot instance is single user and exists only to write the memory image to disk, yes? If so, it seems like we could avoid loading the SELinux policy in this case and avoiding this problem completely.
(In reply to Paul Moore from comment #4)
> It appears that the kernel is having a difficult time allocating kernel
> memory for the SELinux policy load, I'm guessing this is due to memory
> pressure caused by the fact that kernel is a kdump recovery kernel and a
> good portion of the physical memory is reserved for dumping to disk.
>
> Is there any reason why we are loading the SELinux policy in the kdump
> kernel? This kernel boot instance is single user and exists only to write
> the memory image to disk, yes? If so, it seems like we could avoid loading
> the SELinux policy in this case and avoiding this problem completely.
All,
Adding kdump team for response...
ruyang?
Best,
-pbunyan
We load selinux policy when dumping to rootfs, the purpose is to labeling the dump files correctly.
For the oom, Paul, can you retest with kdump.conf option "debug_mem_level 3" so that we can get who is using most of the memory?
Thanks
Dave
In reply to PaulB from comment #12)
> -----------------------------------------------------------
> However, looking at the console log I do see the following:
> -----------------------------------------------------------
> ---<-snip->---
> Loading SELINUX policy
> load_policy invoked oom-killer: gfp_mask=0xd0, order=0, oom_adj=0,
> oom_score_adj=0
Hi Paul,
You should not see these messages with "Release 2.0.0-304".
Following patch removes selinux policy load from kdump kernel.
98f374eeff89 mkdumprd: Remove load_selinux_policy script
~Pratyush
(In reply to Pratyush Anand from comment #13)
> In reply to PaulB from comment #12)
> > -----------------------------------------------------------
> > However, looking at the console log I do see the following:
> > -----------------------------------------------------------
> > ---<-snip->---
> > Loading SELINUX policy
> > load_policy invoked oom-killer: gfp_mask=0xd0, order=0, oom_adj=0,
> > oom_score_adj=0
>
> Hi Paul,
>
> You should not see these messages with "Release 2.0.0-304".
>
> Following patch removes selinux policy load from kdump kernel.
>
> 98f374eeff89 mkdumprd: Remove load_selinux_policy script
>
> ~Pratyush
Pratyush,
You are correct.
The Call Trace in comment #12 is no longer seen:
host: dell-per320-02.khw.lab.eng.bos.redhat.com
distro: RHEL-6.8
kernel: 2.6.32-642.el6
kexec-tools: 2.0.0-304.el6
See here:
https://beaker.engineering.redhat.com/jobs/1558254
Best,
-pbunyan