From: Anna Schumaker <Anna.Schumaker@netapp.com>
To: Chao Yu <yuchao0@huawei.com>, <trond.myklebust@primarydata.com>
Cc: <linux-nfs@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] nfs: add missing CONFIG_MIGRATION for nfs_migrate_page
Date: Mon, 19 Sep 2016 13:38:31 -0400 [thread overview]
Message-ID: <fb5f4957-7d01-4c69-aca2-0e704104d921@Netapp.com> (raw)
In-Reply-To: <20160919120917.29844-1-yuchao0@huawei.com>
Hi Chao,
On 09/19/2016 08:09 AM, Chao Yu wrote:
> We'd better to use CONFIG_MIGRATION to cover nfs_migrate_page, otherwise
> when CONFIG_MIGRATION is not defined, unused nfs_migrate_page will still
> be compiled into kernel.
I don't think that nfs_migrate_page is still compiled into the kernel when CONFIG_MIGRATION=n. The file fs/nfs/internal.h has:
#ifdef CONFIG_MIGRATION
extern int nfs_migrate_page(struct address_space *,
struct page *, struct page *, enum migrate_mode);
#else
#define nfs_migrate_page NULL
#endif
So it looks like we're just setting the variable to a NULL pointer in this case. I'm not opposed to your change, since it better matches how we've done things in other parts of the client, but can you please clean up internal.h while you're at it?
Thanks,
Anna
>
> Signed-off-by: Chao Yu <yuchao0@huawei.com>
> ---
> fs/nfs/file.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/fs/nfs/file.c b/fs/nfs/file.c
> index 7d62097..6cfb83e 100644
> --- a/fs/nfs/file.c
> +++ b/fs/nfs/file.c
> @@ -543,7 +543,9 @@ const struct address_space_operations nfs_file_aops = {
> .invalidatepage = nfs_invalidate_page,
> .releasepage = nfs_release_page,
> .direct_IO = nfs_direct_IO,
> +#ifdef CONFIG_MIGRATION
> .migratepage = nfs_migrate_page,
> +#endif
> .launder_page = nfs_launder_page,
> .is_dirty_writeback = nfs_check_dirty_writeback,
> .error_remove_page = generic_error_remove_page,
>
next prev parent reply other threads:[~2016-09-19 17:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-19 12:09 Chao Yu
2016-09-19 17:38 ` Anna Schumaker [this message]
2016-09-20 0:34 ` Chao Yu
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=fb5f4957-7d01-4c69-aca2-0e704104d921@Netapp.com \
--to=anna.schumaker@netapp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@primarydata.com \
--cc=yuchao0@huawei.com \
/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
all inboxes | Powered by JetHome®