Re: [PATCH v5 0/2] MR5392: win32u: Avoid writing past allocated memory in peek_message().

[Jacek Caban (＠jacek)]

On Tue Mar 26 15:17:58 2024 +0000, Paul Gofman wrote:
> Do we always reallocate to larger size? It is currently reallocated
> based on the actual message size returned by the server, while
> buffer_size in peek_message may be bigger (and it is first allocated to
> 1024 bytes). Granted, I only reproduced the actual memory corruption
> with Proton, but it seems to me that in this regard the handling is the same.

Right, I see, thanks. It's possible in cases where we don't actually need any realloc.