Thanks for merging ZOOKEEPER-5103 @[email protected] .

I have completed a defect analysis of the C client and identified 97
additional actionable issues across 8 distinct classes.

Wrong results and data-integrity hazards = 15
    - Silent data corruption, false successes for unexecuted requests,
queue leaks across reconnections, chroot escapes, and transaction
desynchronization
Hangs and failed failover = 25
    - Deadlocks, infinite reconnection loops, busy-wait spinning,
unbounded TLS loops, and server list failover starvation
Crashes and memory errors = 23
    - Missing `NULL` checks, buffer over-reads during Jute
deserialization, unhandled `SIGPIPE` signals, format string
vulnerabilities, and lifecycle crashes
Races = 13
    - Unsynchronized shared state, stale file descriptors, wakeup pipe
saturation, and multithreaded teardown/SASL concurrency hazards
Silently lost settings = 5
    - Dropped reconfigurations, ignored port/topology updates, and
silent truncation of SASL credentials
Misleading diagnostics = 7
    - Inaccurate error codes, transposed transaction IDs in logs,
invalid latency arithmetic, and misleading `errno` reporting
Build System Defects = 4
    - CMake and Autotools compilation/probe failures, syntax errors,
and static archive symbol collisions
Windows Platform Defects = 5
    -  Flawed pthread emulation, I/O multiplexer issues, missing
symbols, and loopback socket hijacking

I will bring patches for these issues soon, prioritized by severity.

I would also like to mention that this analysis was performed as part
of the design work for a new Rust client implementation option, which
will includes a C shim layer, that can serve as either
- a drop in replacement for the C client, requiring no code changes,
merely a relink for any C/C++ application to pick up the new Rust
core, and
- a Rust native ABI for Rust applications.
With any luck I'll be back to contribute this soon.

On Thu, Sep 17, 2026 at 8:10 AM Andor Molnár <[email protected]> wrote:
>
> Hi all,
>
> We’re looking for somebody with C experience and with some free time to 
> actively maintain the ZooKeeper C client library. I’m happy to offer my +1 
> for committership in exchange.
>
> Regards,
>
> Andor
>
>

-- 
Best regards,
Andrew

Reply via email to