summaryrefslogtreecommitdiff
path: root/tools/perf/util/scripting-engines/trace-event-python.c
diff options
context:
space:
mode:
authorMa Wupeng <mawupeng1@huawei.com>2025-02-17 04:43:28 +0300
committerAndrew Morton <akpm@linux-foundation.org>2025-03-06 08:36:13 +0300
commit773b9a6aa6d38894b95088e3ed6f8a701d9f50fd (patch)
tree832bc244b13b7185acc096b78cb82c609f0fcbf1 /tools/perf/util/scripting-engines/trace-event-python.c
parentb81679b1633aa43c0d973adfa816d78c1ed0d032 (diff)
downloadlinux-773b9a6aa6d38894b95088e3ed6f8a701d9f50fd.tar.xz
mm: memory-hotplug: check folio ref count first in do_migrate_range
If a folio has an increased reference count, folio_try_get() will acquire it, perform necessary operations, and then release it. In the case of a poisoned folio without an elevated reference count (which is unlikely for memory-failure), folio_try_get() will simply bypass it. Therefore, relocate the folio_try_get() function, responsible for checking and acquiring this reference count at first. Link: https://lkml.kernel.org/r/20250217014329.3610326-3-mawupeng1@huawei.com Signed-off-by: Ma Wupeng <mawupeng1@huawei.com> Acked-by: David Hildenbrand <david@redhat.com> Acked-by: Miaohe Lin <linmiaohe@huawei.com> Cc: Michal Hocko <mhocko@suse.com> Cc: Naoya Horiguchi <nao.horiguchi@gmail.com> Cc: Oscar Salvador <osalvador@suse.de> Cc: <stable@vger.kernel.org> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions