sudheerv opened a new pull request #6869: URL: https://github.com/apache/trafficserver/pull/6869
Allow callers explicitly configure and pass in the max buffer sizes when asking for unknown sized memory chunks depending on the usecase instead of relying on a common/global default config. This addresses https://github.com/apache/trafficserver/issues/6850 Email to dev/users@ ``` Removing the config proxy.config.io.max_buffer_size Yahoo / Sent Sudheer Vinukonda <[email protected]> To: Users , Dev Thu, Jun 4 at 12:52 PM The config `proxy.config.io.max_buffer_size` determines the default Max IOBuffer size that's used when the caller (e.g HostDB alloc, POST request buffer) asks for a chunk of memory via the `iobuffer_size_to_index()` or `buffer_size_to_index()` interfaces without explicitly passing in the max IOBuffer. This can cause issues such as https://github.com/apache/trafficserver/issues/6850 or worse memory corruption such as https://github.com/apache/trafficserver/issues/6849 After some discussion with Leif, we think we should let callers explicitly pass in the max buffer sizes when asking for unknown sized memory chunks (e.g proxy.config.http.max_post_size and a new config proxy.config.hostdb.max_buffer.size) and remove the hidden default max io config. Please let us know if there are any concerns/comments. ``` ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
