summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/stackcollapse.py
diff options
context:
space:
mode:
authorQu Wenruo <wqu@suse.com>2026-09-08 16:45:39 +0930
committerDavid Sterba <dsterba@suse.com>2026-10-12 19:16:20 +0200
commit0d8c05fe050ab243489c0b5998e31d7d30003791 (patch)
tree68b308d22b8d64dac5b26708a136d7c62f53c48d /tools/perf/scripts/python/stackcollapse.py
parentb2ba99cf6f7ba3cd53fe6bb1b24a4c8cc5d74ba7 (diff)
downloadlinux-0d8c05fe050ab243489c0b5998e31d7d30003791.tar.gz
linux-0d8c05fe050ab243489c0b5998e31d7d30003791.zip
btrfs: tree-log: use kvmalloc() for overwrite_item()
The @src_copy buffer utilized inside overwrite_item() can be as large as the nodesize. For an existing btrfs with 64KiB nodesize, it means there is a high chance to fail the kmalloc() call if there is not enough physically contiguous pages. Meanwhile there is really no need for such physically contiguous pages, as we only use that buffer to compare the content of the item. Use kvmalloc() to replace the kmalloc() call. For most cases that kvmalloc() call will be easily fulfilled by regular kmalloc(), but for really large items and large nodes, kvmalloc() will have a much higher chance to get memory allocated. Reviewed-by: Daniel Vacek <neelx@suse.com> Reviewed-by: Johannes Thumshirn <johannes.thumshirn@wdc.com> Signed-off-by: Qu Wenruo <wqu@suse.com> Reviewed-by: David Sterba <dsterba@suse.com> Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions