From: Matthew Wilcox <willy@infradead.org>
To: kernel test robot <lkp@intel.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [linux-next:master 11462/12208] mm/internal.h:709:3: error: implicit declaration of function 'release_fault_lock' is invalid in C99
Date: Thu, 24 Aug 2023 02:08:41 +0100 [thread overview]
Message-ID: <ZOatmXjnQ71xJZHu@casper.infradead.org> (raw)
In-Reply-To: <202308240613.DrqV4VT4-lkp@intel.com>
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@intel.com/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.
prev parent reply other threads:[~2023-08-24 1:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-23 22:51 kernel test robot
2023-08-24 1:08 ` Matthew Wilcox [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZOatmXjnQ71xJZHu@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox