Bug 1416716 - mmap: invalid argument during update
Summary: mmap: invalid argument during update
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 24
Hardware: x86_64
OS: Unspecified
Target Milestone: ---
Assignee: Lukas Vrabec
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2017-01-26 10:52 UTC by harrim4n
Modified: 2017-08-08 19:36 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2017-08-08 19:36:09 UTC
Type: Bug

Attachments (Terms of Use)
strace log of dnf update (6.00 MB, text/plain)
2017-01-26 10:52 UTC, harrim4n
no flags Details

Description harrim4n 2017-01-26 10:52:05 UTC
Created attachment 1244696 [details]
strace log of dnf update

Description of problem:
When updating selinux-policy-targeted from 3.13.1 (release 190.23.fc24) to 3.13.1 (release 191.23.fc24), an error occurs:
"mmap: invalid argument"

Version-Release number of selected component (if applicable):
3.13.1 (release 191.23.fc24)

How reproducible:

Steps to Reproduce:
1. Setup Fedora 24 with selinux-policy-targeted version 3.13.1 (release 190.23.fc24)
2. Run "dnf update -y"

Actual results:
An error occurs during the setup. Apparently the package is updated anyway by dnf.

Expected results:
The package is updated.

Additional info:
I ran a strace during the dnf update command. The error occurs after opening the file "/etc/selinux/targeted/contexts/files/file_contexts.local.bin" because its size is 0. See the attached strace.log for more details (line 70746). I removed a "few" lines from the log because it was 73MB big. If you need more context, please tell me and I'll provide the full log.
Before the update, the file has a size of 35 byte, the non-binary version has 0 bytes.
The machine is running on a VMware ESXi, if that is relevant.
I'm assuming that the error occurs during some portion of the selinux package update, I'm not sure if the bug is in selinux or in dnf.

Comment 1 Fedora End Of Life 2017-07-26 00:12:54 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 2 Fedora End Of Life 2017-08-08 19:36:09 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.