Bug 1976022 - SELINUX=disabled in /etc/selinux/config causes criu to not function
Summary: SELINUX=disabled in /etc/selinux/config causes criu to not function
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: criu
Version: 35
Hardware: All
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Adrian Reber
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-06-25 01:58 UTC by Ambrose Chua
Modified: 2021-10-01 01:26 UTC (History)
3 users (show)

Fixed In Version: criu-3.16-2.fc35 criu-3.16-2.fc34
Clone Of:
Environment:
Last Closed: 2021-09-29 00:17:21 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github checkpoint-restore criu issues 1402 0 None closed criu/lsm.c:90: Invalid selinux context kernel 2021-06-25 01:58:50 UTC
Github checkpoint-restore criu pull 1457 0 None closed lsm: handle half initialized SELinux setups 2021-06-25 01:58:50 UTC

Description Ambrose Chua 2021-06-25 01:58:51 UTC 
Description of problem:

See https://github.com/checkpoint-restore/criu/issues/1402
On a system with SELINUX=disabled in /etc/selinux/config, criu fails to start because it checks for the existence of /sys/fs/selinux, which exists in a SELINUX=disabled system.

Version-Release number of selected component (if applicable):
3.15

How reproducible:


Steps to Reproduce:
1. Disable selinux in /etc/selinux/config
2. Install criu
3. Run criu dump -t [PID]

Actual results:
...
Error (criu/lsm.c:90): Invalid selinux context kernel
Error (criu/cr-dump.c:1390): Dump core (pid: 3646715) failed with -1
Error (criu/cr-dump.c:1768): Dumping FAILED.

Expected results:
Successfully dumped

Additional info:
Fixed in upstream, have to wait for them to create a new release: https://github.com/checkpoint-restore/criu/pull/1457/files
Comment 1 Ben Cotton 2021-08-10 13:08:47 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 35 development cycle.
Changing version to 35.
Comment 2 Fedora Update System 2021-09-23 09:58:03 UTC 
FEDORA-2021-a796b20341 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2021-a796b20341
Comment 3 Fedora Update System 2021-09-23 10:00:04 UTC 
FEDORA-2021-776465d958 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-776465d958
Comment 4 Fedora Update System 2021-09-23 19:41:36 UTC 
FEDORA-2021-776465d958 has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-776465d958`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-776465d958

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 5 Fedora Update System 2021-09-24 02:51:28 UTC 
FEDORA-2021-a796b20341 has been pushed to the Fedora 35 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-a796b20341`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-a796b20341

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 6 Fedora Update System 2021-09-29 00:17:21 UTC 
FEDORA-2021-a796b20341 has been pushed to the Fedora 35 stable repository.
If problem still persists, please make note of it in this bug report.
Comment 7 Fedora Update System 2021-10-01 01:26:59 UTC 
FEDORA-2021-776465d958 has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.