Bug #4955
closed
stream: too aggressive pruning in lossy streams
Added by Jeff Lucovsky almost 3 years ago.
Updated almost 3 years ago.
Description
Pruning of StreamBufferBlocks could remove blocks that fell entirely after the target offset due to a logic error. This could lead to data being evicted that was still meant to be processed in the app-layer parsers.
- Copied from Bug #4953: stream: too aggressive pruning in lossy streams added
- Status changed from Assigned to In Progress
Cherry-pick commit(s)
- 258415b23f455e3aaee6d97a0e485e5690959011 (partial)
- 544ff0fb52cad0ee35dfd968bd775703737c4ef6
- 78f5e082f5188204606ab9ceb5044447e49aaca2
- Status changed from In Progress to In Review
Cherry-pick commit 544ff0fb removed per request.
- Status changed from In Review to Closed
Also available in: Atom
PDF