summaryrefslogtreecommitdiffstats
path: root/tools/perf/scripts/python/exported-sql-viewer.py
diff options
context:
space:
mode:
authorFeng Tang <feng.tang@intel.com>2024-10-16 23:41:50 +0800
committerVlastimil Babka <vbabka@suse.cz>2024-11-16 21:18:29 +0100
commit9ef8568bd7cddf59e1ff6ee1b7d799539e331b73 (patch)
tree227e66d7858f0df2a8631d25ca029db15c1eafaf /tools/perf/scripts/python/exported-sql-viewer.py
parentb6da940130579769a42605b2c7f529b6f14ef1f8 (diff)
downloadlinux-stable-9ef8568bd7cddf59e1ff6ee1b7d799539e331b73.tar.gz
linux-stable-9ef8568bd7cddf59e1ff6ee1b7d799539e331b73.tar.bz2
linux-stable-9ef8568bd7cddf59e1ff6ee1b7d799539e331b73.zip
mm/slub: Consider kfence case for get_orig_size()
When 'orig_size' of kmalloc object is enabled by debug option, it should either contains the actual requested size or the cache's 'object_size'. But it's not true if that object is a kfence-allocated one, and the data at 'orig_size' offset of metadata could be zero or other values. This is not a big issue for current 'orig_size' usage, as init_object() and check_object() during alloc/free process will be skipped for kfence addresses. But it could cause trouble for other usage in future. Use the existing kfence helper kfence_ksize() which can return the real original request size. Signed-off-by: Feng Tang <feng.tang@intel.com> Reviewed-by: Hyeonggon Yoo <42.hyeyoo@gmail.com> Signed-off-by: Vlastimil Babka <vbabka@suse.cz>
Diffstat (limited to 'tools/perf/scripts/python/exported-sql-viewer.py')
0 files changed, 0 insertions, 0 deletions