[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Ylb0CGeFJlc4EzLk@7ec4ff11d4ae>
Date: Thu, 14 Apr 2022 00:02:16 +0800
From: kernel test robot <lkp@...el.com>
To: Peter Xu <peterx@...hat.com>
Cc: kbuild-all@...ts.01.org,
Linux Memory Management List <linux-mm@...ck.org>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org
Subject: [RFC PATCH linux-next] 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?
Fixes: 729c63ce2bbd ("mm/shmem: handle uffd-wp during fork()")
Reported-by: kernel test robot <lkp@...el.com>
Signed-off-by: kernel test robot <lkp@...el.com>
---
mm/memory.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mm/memory.c b/mm/memory.c
index a426c46dd6f68..92cca76bcd3ee 100644
--- a/mm/memory.c
+++ b/mm/memory.c
@@ -1234,7 +1234,7 @@ copy_p4d_range(struct vm_area_struct *dst_vma, struct vm_area_struct *src_vma,
* 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)
{
/*
Powered by blists - more mailing lists