Bug 1965985
Summary: | SELinux is preventing kexec from read access on the file /var/lib/kdump/initramfs-*kdump.img | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | ltao | |
Component: | selinux-policy | Assignee: | Zdenek Pytela <zpytela> | |
Status: | CLOSED ERRATA | QA Contact: | Milos Malik <mmalik> | |
Severity: | high | Docs Contact: | ||
Priority: | high | |||
Version: | 8.5 | CC: | dornelas, hshiina, jniu, lvrabec, mmalik, plautrba, ruyang, ssekidde, travier | |
Target Milestone: | beta | Keywords: | AutoVerified, Triaged, ZStream | |
Target Release: | 8.5 | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | selinux-policy-3.14.3-71.el8 | Doc Type: | Enhancement | |
Doc Text: |
Feature:
In the new version of the kexec-tools package, kdump checks if the initramfs image can be created in /boot. If the check fails, the /var/lib/kdump directory is used instead to create the initramfs image.
Reason:
On some operating systems, the /boot directory can be read-only, preventing the initramfs image file from being created in /boot.
Result:
SELinux supports kdump creating initramfs images in /var/lib/kdump.
|
Story Points: | --- | |
Clone Of: | ||||
: | 1976260 (view as bug list) | Environment: | ||
Last Closed: | 2021-11-09 19:43:05 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | ||||
Bug Blocks: | 1918499, 1976260, 1991443, 2011878 |
Description
ltao
2021-05-31 10:11:40 UTC
Needs backporting: commit af7e4b6492b315ee0912aef7f9f2d89a4f681ab6 Author: Zdenek Pytela <zpytela> Date: Mon May 10 18:36:26 2021 +0200 Label /var/lib/kdump with kdump_var_lib_t The kexec-tools usually create initramfs-KERNELVERSIONkdump.img in /boot. On some operating systems, the /boot directory can be read-only, preventing the image file from being created. In newer kexec-tools package versions, the image files are created in /var/lib/kdump in case /boot is read-only. The kdump_manage_lib_files() interface was created and rpm_script_t allowed to manage /var/lib/kdump files. This is needed when the /lib/kernel/install.d/60-kdump.install kernel install hook is triggered to delete unused images. Resolves: rhbz#1951323 (In reply to Zdenek Pytela from comment #1) > Needs backporting: > commit af7e4b6492b315ee0912aef7f9f2d89a4f681ab6 > Author: Zdenek Pytela <zpytela> > Date: Mon May 10 18:36:26 2021 +0200 > > Label /var/lib/kdump with kdump_var_lib_t > > The kexec-tools usually create initramfs-KERNELVERSIONkdump.img in /boot. > On some operating systems, the /boot directory can be read-only, > preventing the image file from being created. In newer kexec-tools > package versions, the image files are created in /var/lib/kdump > in case /boot is read-only. > > The kdump_manage_lib_files() interface was created and rpm_script_t > allowed to manage /var/lib/kdump files. This is needed when the > /lib/kernel/install.d/60-kdump.install kernel install hook is triggered > to delete unused images. > > Resolves: rhbz#1951323 Hello Zdenek, Since the bug blocks bz1918499, which may be delayed for DTM, could you please backport the patch and resolve this bug? Thank you very much! Thanks, Tao Liu > Since the bug blocks bz1918499, which may be delayed for DTM, could you
> please backport the patch and resolve this bug?
Should be in the next build.
*** Bug 1961728 has been marked as a duplicate of this bug. *** I am afraid one more commit is needed: https://github.com/fedora-selinux/selinux-policy/pull/782 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 (selinux-policy bug fix and enhancement update), 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://access.redhat.com/errata/RHBA-2021:4420 |