Re: (ITS#6045) Use copy of db in syncprov_matchops

rein@OpenLDAP.org wrote:

Full_Name: Rein Tollevik Version: CVS HEAD/RE_24 OS: Irrelevant URL: Submission from: (NULL) (81.93.160.250)

I had a couple of seg. faults when resync'ing my servers after upgrading to the upcoming 2.4.16 release. Looks as if a copy of the backend must be used when testing the filter in syncprov_matchops. See the gdb output at the end. Note, some function names are incorrect due to optimization. A fix is coming.

The fix makes no sense, or the problem has not yet been analyzed sufficiently. Nobody in that call chain should be zeroing out bd_info. And if someone *is*, then it will happen in *whatever* BackendDB structure is currently being used.

Explain the real cause of the problem, and why the fix is correct.