[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: (ITS#7723) slapd crashes on multi core machines if a search request is *immediately* followed by an unbind
- To: openldap-its@OpenLDAP.org
- Subject: Re: (ITS#7723) slapd crashes on multi core machines if a search request is *immediately* followed by an unbind
- From: hyc@symas.com
- Date: Fri, 11 Oct 2013 16:53:27 GMT
- Auto-submitted: auto-generated (OpenLDAP-ITS)
michael.vishchers@7p-group.com wrote:
> Full_Name: Michael Vishchers
> Version: 2.4.36
> OS: RHEL 6.3
> URL: ftp://ftp.openldap.org/incoming/
> Submission from: (NULL) (109.41.86.33)
>
>
> The bug mentioned in ITS #7716 unfortunately still persists in 2.4.36.
>
> We now found a way to reproduce it:
>
> - make sure that threads can run freely (i.e., provide enough cpus)
If your client loop is running as a single thread then the number of CPUs and
running threads should be irrelevant. If the number of threads and CPUs matter
then you're misusing the API. Closing this ITS.
> - start slapd with the rwm overlay
> - run a client loop that
> -- binds as a valid user
> -- sends a valid search request that is *immediately* (i.e., don't wait for any
> answers) followed by an unbind request
>
> after several iterations (with 2.4.23 it was between 2 and 7, with 2.4.36 it was
> about 30) slapd crashes in malloc.c
>
>
--
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/