aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/mm/rmap.c
diff options
context:
space:
mode:
authorDavid Hildenbrand <david@redhat.com>2024-07-31 16:20:00 +0200
committerAndrew Morton <akpm@linux-foundation.org>2024-09-01 20:25:57 -0700
commit94ccd21e9a5f41585bd16cc84dab2afa6cc21149 (patch)
treed3543805384a4c1c3accd0500da924fb43e667d7 /mm/rmap.c
parentmm/memory_hotplug: get rid of __ref (diff)
downloadwireguard-linux-94ccd21e9a5f41585bd16cc84dab2afa6cc21149.tar.xz
wireguard-linux-94ccd21e9a5f41585bd16cc84dab2afa6cc21149.zip
mm/hugetlb: remove hugetlb_follow_page_mask() leftover
We removed hugetlb_follow_page_mask() in commit 9cb28da54643 ("mm/gup: handle hugetlb in the generic follow_page_mask code") but forgot to cleanup some leftovers. While at it, simplify the hugetlb comment, it's overly detailed and rather confusing. Stating that we may end up in there during coredumping is sufficient to explain the PF_DUMPCORE usage. Link: https://lkml.kernel.org/r/20240731142000.625044-1-david@redhat.com Signed-off-by: David Hildenbrand <david@redhat.com> Reviewed-by: Peter Xu <peterx@redhat.com> Cc: Muchun Song <muchun.song@linux.dev> Cc: Alexander Viro <viro@zeniv.linux.org.uk> Cc: Christian Brauner <brauner@kernel.org> Cc: Jan Kara <jack@suse.cz> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Diffstat (limited to 'mm/rmap.c')
0 files changed, 0 insertions, 0 deletions