[
https://issues.apache.org/jira/browse/IMPALA-15010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Smith resolved IMPALA-15010.
------------------------------------
Fix Version/s: Impala 5.0.0
Resolution: Fixed
> Patch gperftools to prevent integer wrap when
> tcmalloc_max_total_thread_cache_bytes > INT_MAX
> ---------------------------------------------------------------------------------------------
>
> Key: IMPALA-15010
> URL: https://issues.apache.org/jira/browse/IMPALA-15010
> Project: IMPALA
> Issue Type: Bug
> Components: Infrastructure
> Affects Versions: Impala 5.0.0
> Reporter: Joe McDonnell
> Priority: Major
> Fix For: Impala 5.0.0
>
>
> The size and max_size counters for a thread cache are stored as a 32-bit
> signed integers inside gperftools. With the default
> tcmalloc_max_total_thread_cache_bytes, this doesn't matter. As
> tcmalloc_max_total_thread_cache_bytes goes above INT_MAX, it becomes
> hypothetically possible for the size or max size to wrap and go negative.
> This should be hard to hit, but it would be better to patch gperftools to
> prevent it. In google tcmalloc, they use size_t for the size and max_size
> counters in the thread cache.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
