On Thu, Aug 24, 2023 at 06:51:10AM +0800, kernel test robot wrote: > tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master > head: e3f80d3eae76c3557b3c9b5938ad01c0e6cf25ec > commit: 0790e1e2b1b71ba357e89e779451efe79dff28e6 [11462/12208] mm: allow fault_dirty_shared_page() to be called under the VMA lock > config: um-allyesconfig (https://download.01.org/0day-ci/archive/20230824/202308240613.DrqV4VT4-lkp@xxxxxxxxx/config) ... > In file included from mm/filemap.c:50: > >> mm/internal.h:709:3: error: implicit declaration of function 'release_fault_lock' is invalid in C99 [-Werror,-Wimplicit-function-declaration] > release_fault_lock(vmf); > ^ > 12 warnings and 1 error generated. This is a patch ordering issue (and thus bisection hazard) release_fault_lock() is introduced in d169f9691c08 ("mm: handle swap page faults under per-VMA lock") which is currently ordered after 0790e1e2b1b7. It's architecture independent, and ARCH=um is not the relevant part, nor is clang implicated.
