From: Yang Shi <shy828301@gmail.com>
To: Pu Lehui <pulehui@huawei.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linux MM <linux-mm@kvack.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -next] mm/huge_memory.c: remove unused variable 'count'
Date: Fri, 14 May 2021 11:48:48 -0700 [thread overview]
Message-ID: <CAHbLzkonsd9f=48+cxKOJamNb9e8qpvWJCYDGFB_wNTdET2zmQ@mail.gmail.com> (raw)
In-Reply-To: <20210514065912.71734-1-pulehui@huawei.com>
On Thu, May 13, 2021 at 11:59 PM Pu Lehui <pulehui@huawei.com> wrote:
>
> mm/huge_memory.c:2663:6: warning:
> variable ‘count’ set but not used [-Wunused-but-set-variable]
> 2663 | int count, mapcount, extra_pins, ret;
> | ^~~~~
>
> This variable is not used in function , this commit
> remove it to fix the warning.
Thanks for catching this warning. Not sure why my gcc 10 doesn't catch
this warning at all. What compiler are you using?
Andrew, the compile warning was introduced by my
mm-thp-check-total_mapcount-instead-of-page_mapcount.patch.
>
> Signed-off-by: Pu Lehui <pulehui@huawei.com>
> ---
> mm/huge_memory.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/mm/huge_memory.c b/mm/huge_memory.c
> index 52ca04b905cf..a23a127302e9 100644
> --- a/mm/huge_memory.c
> +++ b/mm/huge_memory.c
> @@ -2660,7 +2660,7 @@ int split_huge_page_to_list(struct page *page, struct list_head *list)
> struct deferred_split *ds_queue = get_deferred_split_queue(head);
> struct anon_vma *anon_vma = NULL;
> struct address_space *mapping = NULL;
> - int count, mapcount, extra_pins, ret;
> + int mapcount, extra_pins, ret;
> pgoff_t end;
>
> VM_BUG_ON_PAGE(is_huge_zero_page(head), head);
> @@ -2737,7 +2737,6 @@ int split_huge_page_to_list(struct page *page, struct list_head *list)
>
> /* Prevent deferred_split_scan() touching ->_refcount */
> spin_lock(&ds_queue->split_queue_lock);
> - count = page_count(head);
> mapcount = total_mapcount(head);
> if (!mapcount && page_ref_freeze(head, 1 + extra_pins)) {
> if (!list_empty(page_deferred_list(head))) {
> --
> 2.17.1
>
>
prev parent reply other threads:[~2021-05-14 18:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-14 6:59 Pu Lehui
2021-05-14 18:48 ` Yang Shi [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='CAHbLzkonsd9f=48+cxKOJamNb9e8qpvWJCYDGFB_wNTdET2zmQ@mail.gmail.com' \
--to=shy828301@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pulehui@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