Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 242930 - semanage crashes adding fcontext
semanage crashes adding fcontext
Product: Fedora
Classification: Fedora
Component: policycoreutils (Show other bugs)
x86_64 Linux
low Severity medium
: ---
: ---
Assigned To: Daniel Walsh
Ben Levenson
Depends On:
  Show dependency treegraph
Reported: 2007-06-06 10:55 EDT by Jared Brothers
Modified: 2008-01-21 10:42 EST (History)
0 users

See Also:
Fixed In Version: Current
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-01-21 10:42:49 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Backtraces of crashed semanage (6.63 KB, text/plain)
2007-06-23 09:55 EDT, Artur
no flags Details

  None (edit)
Description Jared Brothers 2007-06-06 10:55:49 EDT
Description of problem:
The example of adding a file context to the policy taken from
the semanage man page segfaults.

Version-Release number of selected component (if applicable):
setools.x86_64 3.1-4.fc7 fedora 

How reproducible:

Steps to Reproduce:
1. sudo semanage fcontext -a -t httpd_sys_content_t "/web(/.*)?"
   Segmentation fault
2. echo $?
Actual results:
Crash; policy unchanged.

Expected results:
Policy changed.

Additional info:
Comment 1 Artur 2007-06-23 09:55:10 EDT
Created attachment 157682 [details]
Backtraces of crashed semanage

This happens on x86_64 system, but not on 32 bit systems. It happens on every
try of modyfying policy (adding user, port, file context...).
I am attaching a file with backtraces, although I'm not sure if they are
useful. The interesting thing is, that there is always something resembling
null pointer (con, fcontext, handle...)
I'm using targeted policy.
Comment 2 Daniel Walsh 2007-06-26 06:41:48 EDT
Fixed in libsemanage-2.0.3-4.fc7

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