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.

This is RHEL6 counterpart to Fedora bug #984549.

In order to fix #977981, system-config-kdump must be permitted to access the bootloader configuration on systems that boot using EFI. In particular, s-c-kdump (and grubby which is invoked by s-c-kdump) needs write access to /boot/efi/EFI/redhat/grub.cfg. It might be relevant that the EFI partition on /boot/efi has FAT32 file system.

Let me know if you want any other information, I have borrowed EFI-capable laptop to try things out on.

Martin, could you please check if the bug is fixed in the current policy?
(selinux-policy-3.7.19-210.el6.noarch or higher)

You can get the selinux-policy packages from Brew or from here:
http://people.redhat.com/dwalsh/SELinux/RHEL6/noarch/

(In reply to Michal Trunecka from comment #4)
> Martin, could you please check if the bug is fixed in the current policy?

I'm sorry, I already returned the EFI laptop I tested this on.

Ok, we'll leave just as policy check.

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, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-1598.html

(In reply to errata-xmlrpc from comment #8)
I've read the erratum at http://rhn.redhat.com/errata/RHBA-2013-1598.html but I'm unclear on whether the selinux policy changes described in this erratum will be included in future RHEL6.x versions.  Can you clarify please when these policy changes are integrated into new versions?

-fs_read_dos_files(kdumpgui_t)
+fs_manage_dos_files(kdumpgui_t)

has been added to RHEL6.5. So s-c-kdump is allowed to manage files on dosfs_t.