From: SeongJae Park <sj@kernel.org>
To: Junjie Fu <fujunjie1@qq.com>
Cc: SeongJae Park <sj@kernel.org>,
linux-mm@kvack.org, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org, willy@infradead.org,
mhocko@suse.com, gourry@gourry.net
Subject: Re: [PATCH] mempolicy.h: Remove unnecessary header file inclusions
Date: Sat, 7 Dec 2024 11:53:41 -0800 [thread overview]
Message-ID: <20241207195341.279560-1-sj@kernel.org> (raw)
In-Reply-To: <tencent_08B979048FE091821B290B18AE97E70DC507@qq.com>
Hi Junie,
On Fri, 6 Dec 2024 23:53:49 +0800 Junjie Fu <fujunjie1@qq.com> wrote:
> Originally, linux/mempolicy.h included linux/pagemap.h because vma_migratable()
> was implemented inline within the header, requiring mapping_gfp_mask()
> function to implement vma_migratable(). Now that vma_migratable() is only
> declared in linux/mempolicy.h and its implementation has been moved to mempolicy.c,
> the inclusion of linux/pagemap.h in the header is no longer necessary.
>
> Additionally, since mempolicy.c includes internal.h, and internal.h already
> includes linux/pagemap.h, so there is no need to modify mempolicy.c after
> removing the direct inclusion of linux/pagemap.h from linux/mempolicy.h
>
> Signed-off-by: Junjie Fu <fujunjie1@qq.com>
> ---
> include/linux/mempolicy.h | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/include/linux/mempolicy.h b/include/linux/mempolicy.h
> index ce9885e0178a..d36877557b00 100644
> --- a/include/linux/mempolicy.h
> +++ b/include/linux/mempolicy.h
> @@ -12,7 +12,6 @@
> #include <linux/rbtree.h>
> #include <linux/spinlock.h>
> #include <linux/nodemask.h>
> -#include <linux/pagemap.h>
> #include <uapi/linux/mempolicy.h>
I noticed kunit UM build errors as below on mm-unstable, and git bisect points
this patch.
$ ./tools/testing/kunit/kunit.py run --kunitconfig ./mm/damon/tests/
[...]
fs/aio.c:525:71: error: ‘FGP_CREAT’ undeclared (first use in this function); did you mean ‘IPC_CREAT’?
525 | FGP_LOCK | FGP_ACCESSED | FGP_CREAT,
| ^~~~~~~~~
| IPC_CREAT
fs/aio.c:532:17: error: implicit declaration of function ‘folio_end_read’; did you mean ‘folio_test_head’? [-Werror=implicit-function-declaration]
532 | folio_end_read(folio, true);
| ^~~~~~~~~~~~~~
| folio_test_head
[...]
I also confirmed including pagemap.h on fs/aio.c as below fixes the issue. I
would like to hear you or others opinions though, since I'm not familiar with
the inclusion routes of the file.
diff --git a/fs/aio.c b/fs/aio.c
index 50671640b588..9fad51dc823f 100644
--- a/fs/aio.c
+++ b/fs/aio.c
@@ -39,6 +39,7 @@
#include <linux/compat.h>
#include <linux/migrate.h>
#include <linux/ramfs.h>
+#include <linux/pagemap.h>
#include <linux/percpu-refcount.h>
#include <linux/mount.h>
#include <linux/pseudo_fs.h>
Thanks,
SJ
[...]
next prev parent reply other threads:[~2024-12-07 19:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-06 15:53 [PATCH] mempolicy.h: Remove unnecessary header file inclusions Junjie Fu
2024-12-07 6:00 ` Andrew Morton
2024-12-07 8:14 ` [PATCH] mm/mempolicy.c: include pagemap.h directly Junjie Fu
2024-12-07 17:14 ` Matthew Wilcox
2024-12-07 18:22 ` [PATCH] mm/mempolicy.c: include pagemap.h directly in right place Junjie Fu
2024-12-07 19:53 ` SeongJae Park [this message]
2024-12-07 21:55 ` [PATCH] mempolicy.h: Remove unnecessary header file inclusions Matthew Wilcox
2024-12-08 13:50 ` Junjie Fu
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=20241207195341.279560-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=fujunjie1@qq.com \
--cc=gourry@gourry.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=willy@infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.