The patch titled
Subject: mm/shmem: vma_needs_copy can be static
has been added to the -mm tree. Its filename is
mm-shmem-handle-uffd-wp-during-fork-fix.patch
This patch should soon appear at
https://ozlabs.org/~akpm/mmots/broken-out/mm-shmem-handle-uffd-wp-during-fork-fix.patch
and later at
https://ozlabs.org/~akpm/mmotm/broken-out/mm-shmem-handle-uffd-wp-during-fork-fix.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/process/submit-checklist.rst when testing your code ***
The -mm tree is included into linux-next and is updated
there every 3-4 working days
------------------------------------------------------
From: kernel test robot <lkp@xxxxxxxxx>
Subject: mm/shmem: vma_needs_copy can be static
mm/memory.c:1238:1: warning: symbol 'vma_needs_copy' was not declared. Should it be static?
Link: https://lkml.kernel.org/r/Ylb0CGeFJlc4EzLk@7ec4ff11d4ae
Fixes: 729c63ce2bbd ("mm/shmem: handle uffd-wp during fork()")
Signed-off-by: kernel test robot <lkp@xxxxxxxxx>
Reported-by: kernel test robot <lkp@xxxxxxxxx>
Acked-by: Peter Xu <peterx@xxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
--- a/mm/memory.c~mm-shmem-handle-uffd-wp-during-fork-fix
+++ a/mm/memory.c
@@ -1234,7 +1234,7 @@ copy_p4d_range(struct vm_area_struct *ds
* false when we can speed up fork() by allowing lazy page faults later until
* when the child accesses the memory range.
*/
-bool
+static bool
vma_needs_copy(struct vm_area_struct *dst_vma, struct vm_area_struct *src_vma)
{
/*
_
Patches currently in -mm which might be from lkp@xxxxxxxxx are
mm-secretmem-fix-panic-when-growing-a-memfd_secret-fix.patch
mm-shmem-handle-uffd-wp-during-fork-fix.patch
