Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Created attachment 1277312[details]
full st.
Description of problem:
there's a directory crash while creating role cache. At first I thought it could be "bug 1419162 A filtered nsrole that specifies an empty nsrole in its nsRoleFilter will result in a segfault." but this bug is fixed in customer version: 389-ds-base-1.3.5.10-20
The problem is that customer cannot give us the core file because of confidentiality.
We see in the stack trace:
Thread 1 (Thread 0x7ff7502478c0 (LWP 6591)):
#0 0x00007ff7427c4d68 in strcmpi_fast (src=0x7ff7427c6fe3 "nsRole", dst=0x1 <Address 0x1 out of bounds>) at ldap/servers/slapd/intrinsics.h:29
f = <optimized out>
l = <optimized out>
#1 roles_check_filter (filter_list=0x7ff76fcbbb80) at ldap/servers/plugins/roles/roles_cache.c:1089
f = 0x7ff76fcbbc80
type = 0x0
#2 roles_cache_create_object_from_entry (hint=0, result=<synthetic pointer>, role_entry=0x7ff76fb992c0) at ldap/servers/plugins/roles/roles_cache.c:1277
filter = 0x7ff76fcbbb80
filter_attr_value = 0x7ff751828640 "(&(|(objectclass=govermentalapplicationprocess)(networkuser=app::*))(userpassword=*))"
pb = <optimized out>
parent = 0x0
rc = 0
type = <optimized out>
this_role = 0x7ff76fc5aac0
rolescopeDN = <optimized out>
So, we can deduce that in
static int roles_check_filter(Slapi_Filter *filter_list)
{
Slapi_Filter *f;
char *type = NULL;
for ( f = slapi_filter_list_first( filter_list );
f != NULL;
f = slapi_filter_list_next( filter_list, f ) )
{
slapi_filter_get_attribute_type(f, &type);
if (strcasecmp(type, NSROLEATTR) == 0){
return -1;
}
}
return 0;
}
while browsing the Slapi_Filter object that was built from:
"(&(|(objectclass=govermentalapplicationprocess)(networkuser=app::*))(userpassword=*))"
one of the attribute types is corrupted.
I could try to ask the customer to run gdb and get more information if needed.
I will attach full pstack.
Version-Release number of selected component (if applicable): 389-ds-base-1.3.5.10-20
I could reproduce the crash using dirsrvtests/tests/tickets/ticket49122_test.py and replacing the nsrole filter with:
"(&(|(objectclass=govermentalapplicationprocess)(networkuser=app::*))(userpassword=*))"
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://access.redhat.com/errata/RHBA-2017:2086