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.
Bug 1267296 - ns-slapd crash double free in pagedresults_cleanup
Summary: ns-slapd crash double free in pagedresults_cleanup
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: 389-ds-base
Version: 6.8
Hardware: All
OS: Linux
urgent
urgent
Target Milestone: rc
: ---
Assignee: Noriko Hosoi
QA Contact: Viktor Ashirov
Petr Bokoc
URL:
Whiteboard:
Depends On:
Blocks: 1268772
TreeView+ depends on / blocked
 
Reported: 2015-09-29 14:58 UTC by German Parente
Modified: 2020-09-13 21:33 UTC (History)
8 users (show)

Fixed In Version: 389-ds-base-1.2.11.15-67.el6
Doc Type: Bug Fix
Doc Text:
*ns-slapd* no longer crashes when freeing a search results object Previously, when Directory Server freed a search results object, there was a brief period of time before the freed information was set to the `pagedresults` handle. If the `paged-results` handle was released due to a timeout in during this period, a double free event occured, causing *ns-slapd* to crash. This problem has been eliminated and double free no longer occurs when freeing search results objects.
Clone Of:
: 1268772 (view as bug list)
Environment:
Last Closed: 2016-05-10 19:21:30 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github 389ds 389-ds-base issues 1630 0 None None None 2020-09-13 21:33:19 UTC
Red Hat Bugzilla 1247792 1 None None None 2021-01-20 06:05:38 UTC
Red Hat Product Errata RHBA-2016:0737 0 normal SHIPPED_LIVE 389-ds-base bug fix and enhancement update 2016-05-10 22:29:13 UTC

Internal Links: 1247792

Description German Parente 2015-09-29 14:58:28 UTC 
Description of problem:

customer is experiencing a crash using rhel6.7, more precisely, using release 60 + fix for crash paged searches with this signature:

Thread 1 (Thread 0x7f1d8d66a7c0 (LWP 26260)):
#0  0x0000003195432625 in raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
        resultvar = 0
        pid = <value optimized out>
        selftid = 26260
#1  0x0000003195433e05 in abort () at abort.c:92
        save_stage = 2
        act = {__sigaction_handler = {sa_handler = 0x7fffd7ed4bd8, sa_sigaction = 0x7fffd7ed4bd8}, sa_mask = {__val = {140736816040896, 140736816053753, 18, 212958803342, 3, 140736816040906, 6, 212958803346, 2, 140736816040894, 2, 212958796611, 1, 212958803342, 3, 140736816040902}}, sa_flags = 10, sa_restorer = 0x3195557592}
        sigs = {__val = {32, 0 <repeats 15 times>}}
#2  0x0000003195470537 in __libc_message (do_abort=2, fmt=0x3195558780 "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:198
        ap = {{gp_offset = 40, fp_offset = 48, overflow_arg_area = 0x7fffd7ed5540, reg_save_area = 0x7fffd7ed5450}}
        ap_copy = {{gp_offset = 16, fp_offset = 48, overflow_arg_area = 0x7fffd7ed5540, reg_save_area = 0x7fffd7ed5450}}
        fd = 2
        on_2 = <value optimized out>
        list = <value optimized out>
        nlist = <value optimized out>
        cp = <value optimized out>
        written = <value optimized out>
#3  0x0000003195475e66 in malloc_printerr (action=3, str=0x319555686e "free(): invalid pointer", ptr=<value optimized out>) at malloc.c:6336
        buf = "00007f1cf000dd10"
        cp = <value optimized out>
#4  0x0000003aa664c416 in slapi_ch_free (ptr=0x7f1cf0003ee0) at ldap/servers/slapd/ch_malloc.c:363
No locals.
#5  0x00007f1d886b7ccd in delete_search_result_set (pb=0x0, sr=0x7f1d34022a18) at ldap/servers/slapd/back-ldbm/ldbm_search.c:1897
        rc = 0
        filt_errs = 0
#6  0x0000003aa668fe30 in pagedresults_cleanup (conn=0x7f1d73104cd0, needlock=0) at ldap/servers/slapd/pagedresults.c:764
        rc = <value optimized out>
        i = <value optimized out>
        prp = 0x7f1d34022a10
#7  0x0000000000414a00 in connection_cleanup (conn=0x7f1d73104cd0) at ldap/servers/slapd/connection.c:207
No locals.
#8  0x0000000000415971 in connection_table_move_connection_out_of_active_list (ct=0x21acfe0, c=0x7f1d73104cd0) at ldap/servers/slapd/conntable.c:322
No locals.
#9  0x000000000041849e in setup_pr_read_pds (ports=0x7fffd7ed5be0) at ldap/servers/slapd/daemon.c:1708
        add_fd = <value optimized out>
        c = 0x7f1d73104cd0
        socketdesc = 0
        count = 38
        next = 0x7f1d73105e50
        accept_new_connections = <value optimized out>
        slapdFrontendConfig = <value optimized out>
        max_threads_per_conn = 5
        n_listeners = <value optimized out>
        last_accept_new_connections = 1
#10 slapd_daemon (ports=0x7fffd7ed5be0) at ldap/servers/slapd/daemon.c:1165

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

389-ds-base-1.2.11.15-60.2.el6_7.x86_64


How reproducible: very rarely.


Steps to Reproduce:

unknown.


Additional info:

The full stack trace can be found in bz 1247792
Comment 11 errata-xmlrpc 2016-05-10 19:21:30 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
Note You need to log in before you can comment on or make changes to this bug.