Bug 1431207
| Summary: | ns-slapd killed by SIGABRT | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Viktor Ashirov <vashirov> | ||||||
| Component: | 389-ds-base | Assignee: | wibrown <wibrown> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Viktor Ashirov <vashirov> | ||||||
| Severity: | urgent | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 7.4 | CC: | mreynolds, nhosoi, nkinder, rmeggins | ||||||
| Target Milestone: | rc | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | 389-ds-base-1.3.6.1-5.el7 | Doc Type: | If docs needed, set a value | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2017-08-01 21:14:10 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: | |||||||||
| Attachments: |
|
||||||||
|
Description
Viktor Ashirov
2017-03-10 15:23:51 UTC
Created attachment 1261953 [details] coredump.bz2 I think I need a test to help with this. It looks like something is putting a stack value into the vattr map, which triggers the abort on free. (can't free off the stack). If we have a test to reproduce this, that would make this a lot easier to track down and resolve, but I can see how the memory leak fixes would resolve this. The issue is we shouldn't just roll back this fix because we have a lot of leaks, and we need these fixes. It's just a pain that we found it so late :( Is this fixed? I don't see an upstream ticket? I can't reproduce it with the new build. Looks like coverity fixes helped. Build tested: 389-ds-base-1.3.6.1-6.el7.x86_64 No crashes were observed with this build, marking as VERIFIED. 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 |