https://bugs.openldap.org/show_bug.cgi?id=9288
--- Comment #3 from tero.saarni(a)est.tech ---
I might have bumped into a variant of this problem. In my case, I have a
reproducible test for this, and it reproduces crash even after #9400 is
applied.
The assert can be triggered by sending InvalidCredentials response from the
remote server after back-ldap retries the connection and binds again.
This bug might possibly related to another bug that I'm observing: back-ldap
retries bind as anonymous even if `rebind-as-user` is set to yes. I did not
find existing issue for this in
bugs.openldap.org yet.
Log file has:
slapd: bind.c:191: ldap_back_conn_delete: Assertion `!LDAP_BACK_CONN_TAINTED(
lc )' failed.
And backtrace from gdb:
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1 0x00007f587d350859 in __GI_abort () at abort.c:79
#2 0x00007f587d350729 in __assert_fail_base (fmt=0x7f587d4e6588 "%s%s%s:%u:
%s%sAssertion `%s' failed.\n%n",
assertion=0x55740debf839 "!LDAP_BACK_CONN_TAINTED( lc )",
file=0x55740debf7a0 "bind.c", line=191, function=<optimized out>) at
assert.c:92
#3 0x00007f587d361f36 in __GI___assert_fail (assertion=0x55740debf839
"!LDAP_BACK_CONN_TAINTED( lc )", file=0x55740debf7a0 "bind.c",
line=191,
function=0x55740debfff0 <__PRETTY_FUNCTION__.12907>
"ldap_back_conn_delete") at assert.c:101
#4 0x000055740dd857a1 in ldap_back_conn_delete (li=0x55740e2a4c90,
lc=0x7f586c102fa0) at bind.c:191
#5 0x000055740dd862ad in ldap_back_freeconn (li=0x55740e2a4c90,
lc=0x7f586c102fa0, dolock=0) at bind.c:510
#6 0x000055740dd8a795 in ldap_back_retry (lcp=0x7f587ae77810,
op=0x7f5870000bb0, rs=0x7f587ae78a30, sendok=LDAP_BACK_DONTSEND) at bind.c:2035
#7 0x000055740dd48efc in ldap_back_search (op=0x7f5870000bb0,
rs=0x7f587ae78a30) at search.c:579
#8 0x000055740dc91a31 in fe_op_search (op=0x7f5870000bb0, rs=0x7f587ae78a30)
at search.c:406
#9 0x000055740dc91229 in do_search (op=0x7f5870000bb0, rs=0x7f587ae78a30) at
search.c:247
#10 0x000055740dc8d6a7 in connection_operation (ctx=0x7f587ae78b90,
arg_v=0x7f5870000bb0) at connection.c:1168
#11 0x000055740dc8ddd4 in connection_read_thread (ctx=0x7f587ae78b90, argv=0xb)
at connection.c:1319
#12 0x000055740de82e10 in ldap_int_thread_pool_wrapper (xpool=0x55740e243540)
at tpool.c:1051
#13 0x00007f587d526609 in start_thread (arg=<optimized out>) at
pthread_create.c:477
#14 0x00007f587d44d293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
--
You are receiving this mail because:
You are on the CC list for the issue.