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.
Bug 1026661 - avc: denied { search } for pid=28072 comm="portreserve" name="sss"
Summary: avc: denied { search } for pid=28072 comm="portreserve" name="sss"
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: selinux-policy
Version: 7.0
Hardware: All
OS: Linux
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Miroslav Grepl
QA Contact: Milos Malik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-05 07:56 UTC by Petr Sklenar
Modified: 2014-06-18 02:28 UTC (History)
2 users (show)

Fixed In Version: selinux-policy-3.12.1-109.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-13 12:10:36 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Petr Sklenar 2013-11-05 07:56:56 UTC
Description of problem:
there si avc denial when running systemctl restart  portreserve.service


Version-Release number of selected component (if applicable):
Red Hat Enterprise Linux Server release 7.0 Beta (Maipo)
kernel-3.10.0-33.el7.x86_64
selinux-policy-3.12.1-95.el7.noarch
systemd-207-4.el7.x86_64
portreserve-0.0.5-7.el7.x86_64
sssd-common-1.11.1-2.el7.x86_64

How reproducible:
thatss strange.
I can see the issue only once when running in the beaker.
Its reproducible only if you clone the beaker job

Steps to Reproduce:
1. systemctl restart  portreserve.service


Actual results:
avc denial:
https://beaker.engineering.redhat.com/recipes/1115587#task16987703
https://beaker.engineering.redhat.com/recipes/1115408#task16985824

----
time->Mon Nov  4 11:48:36 2013
type=SYSCALL msg=audit(1383583716.655:1019): arch=c000003e syscall=42 success=no exit=-13 a0=4 a1=7fff86aac1c0 a2=6e a3=7fff86aabe90 items=0 ppid=1 pid=5187 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="portreserve" exe="/usr/sbin/portreserve" subj=system_u:system_r:portreserve_t:s0 key=(null)
type=AVC msg=audit(1383583716.655:1019): avc:  denied  { search } for  pid=5187 comm="portreserve" name="sss" dev="dm-1" ino=135650791 scontext=system_u:system_r:portreserve_t:s0 tcontext=system_u:object_r:sssd_var_lib_t:s0 tclass=dir


Expected results:
no denial

Additional info:
/var/lib/sss is inod 135650791

Comment 3 Miroslav Grepl 2013-11-25 10:16:13 UTC
Are you getting more AVC msgs in permissive mode if you re-test it?

Comment 4 Milos Malik 2013-12-06 14:29:35 UTC
There are no additional AVCs in permissive mode.

Comment 6 Ludek Smid 2014-06-13 12:10:36 UTC
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.


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