Bug 480054 - semodule crashes on an empty file
Summary: semodule crashes on an empty file
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: policycoreutils
Version: 11
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Daniel Walsh
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-01-14 18:53 UTC by Bill Nottingham
Modified: 2014-03-17 03:17 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-03-11 16:36:34 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Bill Nottingham 2009-01-14 18:53:56 UTC
Description of problem:

[root@nostromo ~]# touch foo ; semodule -i foo
Segmentation fault

...
open("foo", O_RDONLY)                   = 4
fcntl(4, F_GETFL)                       = 0x8000 (flags O_RDONLY|O_LARGEFILE)
fstat(4, {st_mode=S_IFREG|0644, st_size=0, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7fa954010000
lseek(4, 0, SEEK_CUR)                   = 0
mmap(NULL, 266240, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7fa953faa000
read(4, ""..., 4096)                    = 0
read(4, ""..., 4096)                    = 0
munmap(0x7fa953faa000, 266240)          = 0
fstat(4, {st_mode=S_IFREG|0644, st_size=0, ...}) = 0
mmap(NULL, 0, PROT_READ, MAP_PRIVATE, 4, 0) = -1 EINVAL (Invalid argument)
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++

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

policycoreutils-2.0.61-1.fc11.x86_64

Comment 1 Bug Zapper 2009-06-09 10:43:18 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 3 Daniel Walsh 2010-03-11 16:36:34 UTC
Fixed in policycoreutils-2.0.78-20.fc12


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