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.

Description of problem:
 * it should most likely run in the same domain as other LVM daemons

Version-Release number of selected component (if applicable):
lvm2-2.02.130-5.el7.x86_64
lvm2-cluster-2.02.130-5.el7.x86_64
lvm2-libs-2.02.130-5.el7.x86_64
lvm2-lockd-2.02.130-5.el7.x86_64
lvm2-python-libs-2.02.130-5.el7.x86_64
lvm2-sysvinit-2.02.130-5.el7.x86_64
selinux-policy-3.13.1-60.el7.noarch
selinux-policy-devel-3.13.1-60.el7.noarch
selinux-policy-doc-3.13.1-60.el7.noarch
selinux-policy-minimum-3.13.1-60.el7.noarch
selinux-policy-mls-3.13.1-60.el7.noarch
selinux-policy-sandbox-3.13.1-60.el7.noarch
selinux-policy-targeted-3.13.1-60.el7.noarch

How reproducible:
always

Steps to Reproduce:
1. get a RHEL-7.2 machine with active targeted policy
2. install the lvm2-lockd package
3. service lvm2-lvmlockd start
4. check the context of lvmlockd process

Actual results:
system_u:system_r:unconfined_service_t:s0 root 4824 1  0 16:11 ?       00:00:00 /usr/sbin/lvmlockd -f

Expected results:
system_u:system_r:lvm_t:s0 root 4824 1  0 16:11 ?       00:00:00 /usr/sbin/lvmlockd -f

Additional info:
# matchpathcon `which lvmlockd`
/usr/sbin/lvmlockd	system_u:object_r:bin_t:s0
#

Fixed in Fedora:
commit bc09818bb7b2203edcd0ce9f0bd3f10b79159dc5
Author: Lukas Vrabec <lvrabec>
Date:   Thu Dec 3 12:39:18 2015 +0100

    Label /usr/sbin/lvmlockd binary file as lvm_exec_t. BZ(1287739)

commit 91d25621d4a5d2d12fefce6ddb083b72604d198e
Author: Lukas Vrabec <lvrabec>
Date:   Thu Dec 3 12:39:18 2015 +0100

    Label /usr/sbin/lvmlockd binary file as lvm_exec_t.
    Resolves: rhbz#1278028

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-2283.html