OpenLDAP
Up to top level
Build   Contrib   Development   Documentation   Historical   Incoming   Software Bugs   Software Enhancements   Web  

Logged in as guest

Viewing Incoming/6897
Full headers

From: tarbuck@futurewest.ca
Subject: segfault in lber on close
Compose comment
Download message
State:
0 replies:
1 followups: 1

Major security issue: yes  no

Notes:

Notification:


Date: Fri, 08 Apr 2011 15:18:31 +0000
From: tarbuck@futurewest.ca
To: openldap-its@OpenLDAP.org
Subject: segfault in lber on close
Full_Name: Daniel Tarbuck
Version: 2.4.24
OS: Gentoo Linux
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (209.52.149.70)


slapd[18256]: segfault at 6172752b ip b73fac81 sp bff68718 error 4 in
libc-2.11.3.so[b738c000+13d000]
slapd[7490]: segfault at 6172752b ip b74fac81 sp bfdecb08 error 4 in
libc-2.11.3.so[b748c000+13d000]
slapd[2865]: segfault at 6172752b ip b7c9cc81 sp bfffe5b8 error 4 in
libc-2.11.3.so[b7c2e000+13d000]
slapd[4740]: segfault at 6172752b ip b742cc81 sp bf824e68 error 4 in
libc-2.11.3.so[b73be000+13d000]
slapd[8020]: segfault at 6172752b ip b7c9cc81 sp bfffe5b8 error 4 in
libc-2.11.3.so[b7c2e000+13d000]
slapcat[28227]: segfault at 6172752b ip b742fc81 sp bff45118 error 4 in
libc-2.11.3.so[b73c1000+13d000]


backtrace shows what looks to be a double free() call from lber.

This is a production system, so I don't have a whole lot of information (fixing
was the priority).

The segfault would occur right at the end of execution (closing the db).

using berkdb 4.8 backend.

No problems after reverting to 2.4.23.

Followup 1

Download message
From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
Date: Mon, 9 May 2011 16:17:44 +0200
To: tarbuck@futurewest.ca
Cc: openldap-its@openldap.org
Subject: Re: (ITS#6897) segfault in lber on close
tarbuck@futurewest.ca writes:
> backtrace shows what looks to be a double free() call from lber.
> This is a production system, so I don't have a whole lot of
> information (fixing was the priority).

Well, can you show that backtrace?  Otherwise there's no chance at all
of investigating this further.  slapd uses liblber for a lot of its
allocations, so the double free could come from just about anywhere.

-- 
Hallvard


Up to top level
Build   Contrib   Development   Documentation   Historical   Incoming   Software Bugs   Software Enhancements   Web  

Logged in as guest


The OpenLDAP Issue Tracking System uses a hacked version of JitterBug

______________
© Copyright 2013, OpenLDAP Foundation, info@OpenLDAP.org