Bug 2236902

Summary: RHEL-7.9 OpenLDAP server 2.4.44-25.el7_9 crash in test_filter filterentry.c:69
Product: Red Hat Enterprise Linux 7 Reporter: Marc Sauton <msauton>
Component: openldapAssignee: LDAP Maintainers <idm-ds-dev-bugs>
Status: CLOSED MIGRATED QA Contact: LDAP QA Team <idm-ds-qe-bugs>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 7.9CC: fhirtz, idm-ds-dev-bugs
Target Milestone: rcKeywords: MigratedToJIRA
Target Release: ---Flags: pm-rhel: mirror+
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-09-19 15:42:05 UTC 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 Marc Sauton 2023-09-01 23:24:19 UTC
Description of problem:

Program terminated with signal 11, Segmentation fault.
#0  test_filter (op=op@entry=0x2ba29d35cf30, e=0x2ba30431f558, f=0x0) at filterentry.c:69
69        if ( f->f_choice & SLAPD_FILTER_UNDEFINED ) {
...
(gdb) l
64        Filter    *f )
65    {
66        int    rc;
67        Debug( LDAP_DEBUG_FILTER, "=> test_filter\n", 0, 0, 0 );
68    
69        if ( f->f_choice & SLAPD_FILTER_UNDEFINED ) {
70            Debug( LDAP_DEBUG_FILTER, "    UNDEFINED\n", 0, 0, 0 );
71            rc = SLAPD_COMPARE_UNDEFINED;
72            goto out;
73        }
(gdb) bt
#0  test_filter (op=op@entry=0x2ba29d35cf30, e=0x2ba30431f558, f=0x0) at filterentry.c:69
#1  0x00002ba034e86598 in syncprov_matchops (op=op@entry=0x2ba29d35e510, opc=opc@entry=0x2ba2a8000998, 
    saveit=saveit@entry=0) at syncprov.c:1334
#2  0x00002ba034e880cb in syncprov_op_response (op=0x2ba29d35e510, rs=<optimized out>) at syncprov.c:1972
#3  0x000055651ffff423 in slap_response_play (op=op@entry=0x2ba29d35e510, rs=rs@entry=0x2ba29d35dd70)
    at result.c:508
#4  0x000055651ffff9e0 in send_ldap_response (op=op@entry=0x2ba29d35e510, rs=rs@entry=0x2ba29d35dd70)
    at result.c:583
#5  0x0000556520000572 in slap_send_ldap_result (op=0x2ba29d35e510, rs=0x2ba29d35dd70) at result.c:861
...


this signature seems to match an old bug report at
https://bugs.openldap.org/show_bug.cgi?id=8013

which was 
fixed in master
fixed in RE25
fixed in RE24

and this fix appears to be in openldap-servers-2.4.44-25.el7_9 :

./openldap-2.4.44/CHANGES:      Fixed slapo-syncprov synprov_matchops usage of test_filter (ITS#8013)

so there may be something else or the fix was not complete.

I do not know how to reproduce this event.


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

RHEL-7.9
redhat-release-server-7.9-6.el7_9.x86_64
openldap-servers-2.4.44-25.el7_9.x86_64


How reproducible:
N/A
in the report: slapd is crashing multiple times per week


Steps to Reproduce:
1. N/A
2.
3.

Actual results:


Expected results:


Additional info:

Comment 3 Frank Hirtz 2023-09-04 13:41:18 UTC
Thank you for this. We don't presently have a reproducer, nor do we know why the issue is now being seen as the environment is quite mature at this point. We'll see if we can come up with something, but at present the issue has been sporadic across a pool of servers with no obvious change or trigger.

Comment 4 RHEL Program Management 2023-09-19 14:56:44 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 5 RHEL Program Management 2023-09-19 15:42:05 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.