From: kernel test robot <lkp@intel.com>
To: Yang Shi <shy828301@gmail.com>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [linux-next:master 3032/3150] mm/huge_memory.c:2345:7: warning: variable 'unmap_success' set but not used
Date: Tue, 18 May 2021 02:15:44 +0800 [thread overview]
Message-ID: <202105180239.QzfEH2XD-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2892 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: cd557f1c605fc5a2c0eb0b540610f50dc67dd849
commit: 69cc52577e67f437b4faaa2024faa279fabd2904 [3032/3150] mm: thp: check total_mapcount instead of page_mapcount
config: i386-randconfig-r006-20210517 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=69cc52577e67f437b4faaa2024faa279fabd2904
git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git fetch --no-tags linux-next master
git checkout 69cc52577e67f437b4faaa2024faa279fabd2904
# save the attached .config to linux build tree
make W=1 W=1 ARCH=i386
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
mm/huge_memory.c: In function 'unmap_page':
>> mm/huge_memory.c:2345:7: warning: variable 'unmap_success' set but not used [-Wunused-but-set-variable]
2345 | bool unmap_success;
| ^~~~~~~~~~~~~
mm/huge_memory.c: In function 'split_huge_page_to_list':
>> mm/huge_memory.c:2663:6: warning: variable 'count' set but not used [-Wunused-but-set-variable]
2663 | int count, mapcount, extra_pins, ret;
| ^~~~~
vim +/unmap_success +2345 mm/huge_memory.c
e9b61f19858a5d Kirill A. Shutemov 2016-01-15 2340
906f9cdfc2a080 Hugh Dickins 2018-11-30 2341 static void unmap_page(struct page *page)
e9b61f19858a5d Kirill A. Shutemov 2016-01-15 2342 {
013339df116c2e Shakeel Butt 2020-12-14 2343 enum ttu_flags ttu_flags = TTU_IGNORE_MLOCK |
c7ab0d2fdc8402 Kirill A. Shutemov 2017-02-24 2344 TTU_RMAP_LOCKED | TTU_SPLIT_HUGE_PMD;
666e5a406c3ed5 Minchan Kim 2017-05-03 @2345 bool unmap_success;
e9b61f19858a5d Kirill A. Shutemov 2016-01-15 2346
e9b61f19858a5d Kirill A. Shutemov 2016-01-15 2347 VM_BUG_ON_PAGE(!PageHead(page), page);
e9b61f19858a5d Kirill A. Shutemov 2016-01-15 2348
baa355fd331424 Kirill A. Shutemov 2016-07-26 2349 if (PageAnon(page))
b5ff8161e37cef Naoya Horiguchi 2017-09-08 2350 ttu_flags |= TTU_SPLIT_FREEZE;
baa355fd331424 Kirill A. Shutemov 2016-07-26 2351
666e5a406c3ed5 Minchan Kim 2017-05-03 2352 unmap_success = try_to_unmap(page, ttu_flags);
e9b61f19858a5d Kirill A. Shutemov 2016-01-15 2353 }
e9b61f19858a5d Kirill A. Shutemov 2016-01-15 2354
:::::: The code at line 2345 was first introduced by commit
:::::: 666e5a406c3ed562e7b3ceff8b631b6067bdaead mm: make ttu's return boolean
:::::: TO: Minchan Kim <minchan@kernel.org>
:::::: CC: Linus Torvalds <torvalds@linux-foundation.org>
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 42233 bytes --]
reply other threads:[~2021-05-17 18:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202105180239.QzfEH2XD-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=shy828301@gmail.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;
as well as URLs for NNTP newsgroup(s).