Bug 1067070

Summary:	[RFE] Overview/optimize usage of selinux in lvm2 code base
Product:	[Community] LVM and device-mapper	Reporter:	Zdenek Kabelac <zkabelac>
Component:	lvm2	Assignee:	LVM Team <lvm-team>
lvm2 sub component:	Other	QA Contact:	cluster-qe <cluster-qe>
Status:	NEW ---	Docs Contact:
Severity:	unspecified
Priority:	unspecified	CC:	agk, bmarzins, bmr, dwysocha, heinzm, jbrassow, jonathan, lvm-team, msnitzer, prajnoha, zkabelac
Version:	0-beta1	Flags:	rule-engine: lvm-technical-solution? rule-engine: lvm-test-coverage?
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Zdenek Kabelac 2014-02-19 15:50:46 UTC

Description of problem:

Using selinux with lvm2 seems to be quite expensive and cases noticeable slowdown of the total execution time.

Usage of selinux call should be reviewed and eventually optimized when possible.

Currently lvm2 always calls selabel_open() even when lvm2 does not create any devices (udev now takes care of this) and uses this for creation of file which should be most probably handled by policy.


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

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info: