Bug 1236156

Summary: Avoid using regex in ACL if possible.
Product: Red Hat Enterprise Linux 6 Reporter: Noriko Hosoi <nhosoi>
Component: 389-ds-baseAssignee: Noriko Hosoi <nhosoi>
Status: CLOSED ERRATA QA Contact: Viktor Ashirov <vashirov>
Severity: low Docs Contact: Petr Bokoc <pbokoc>
Priority: low    
Version: 6.0CC: amsharma, jgalipea, lkrispen, nkinder, pbokoc, rmeggins
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 389-ds-base-1.2.11.15-67.el6 Doc Type: Bug Fix
Doc Text:
Improved ACL performance Previously, unnecessarily complicated regular expressions were used in the Access Control List (ACL) implementation in Directory Server. These regular expressions have been removed and the ACL implementation reworked, resulting in improved performance.
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-05-10 19:19:38 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
perf top output
none
perf data file none

Description Noriko Hosoi 2015-06-26 17:42:14 UTC
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/389/ticket/48175

Too expensive for the acl operation?
{{{
$ egrep _re_ acl/*.[ch]
acl/acl.c:	re = slapi_re_comp( pat, &re_result );
acl/acl.c:	/* slapi_re_exec() returns 1 if the string p1 matches the last compiled
acl/acl.c:	rc = slapi_re_exec( re, realval, -1 /* no timelimit */ );
acl/acl.c:	slapi_re_free(re);
}}}

Comment 4 Amita Sharma 2016-01-06 10:00:18 UTC
Created attachment 1112056 [details]
perf top output

Comment 5 Amita Sharma 2016-01-06 12:17:21 UTC
Created attachment 1112131 [details]
perf data file

Comment 6 Amita Sharma 2016-01-06 12:18:00 UTC
PFA, hence the bug is verified.

Comment 8 errata-xmlrpc 2016-05-10 19:19:38 UTC
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-0737.html