Handle overflow in rd_buf_write_remains#4689
Handle overflow in rd_buf_write_remains#4689Emanuele Sabellico (emasab) merged 7 commits intomasterfrom
Conversation
a1622dd to
66fa00b
Compare
|
Hi Emanuele Sabellico (@emasab), Could you please review and approve this PR? It's critical for us as it addresses a blocking issue with the confluent-kafka-dotnet library update. Your approval is eagerly awaited. |
|
There also a problem in My proposed solution is to add a |
Makes sense. I'll create a separate PR to handle that. |
|
Anchit Jain (@anchitj) better to do it here, as it's basically the same thing that is missing |
e5886a9 to
4071f8b
Compare
5bb225f to
daab8b9
Compare
daab8b9 to
396f7cc
Compare
Emanuele Sabellico (emasab)
left a comment
There was a problem hiding this comment.
Thanks Anchit, some changes are needed
4c0d964 to
125846c
Compare
125846c to
4842503
Compare
Emanuele Sabellico (emasab)
left a comment
There was a problem hiding this comment.
Thanks Anchit! Let's wait for the CI and then we can merge this.
|
Could this affect the |
After the implementation of KIP-320, TopicCnt was sent as a varint in the metadata request. This change caused an overflow issue due to the use of
rd_buf_eraseto erase the remaining bytes. The overflow occurred in the calculationrbuf->rbuf_size - (rbuf->rbuf_len + rbuf->rbuf_erased)becauserbuf->rbuf_erasedwas non-zero when the buffer was almost full, leading to an overflow condition.As a result, for certain configurations that caused the buffer to be nearly full, the client was unable to send metadata requests, and it also caused crashes in the .NET client.