From: kernel test robot <lkp@intel.com>
To: Ryan Roberts <ryan.roberts@arm.com>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Barry Song <v-songbaohua@oppo.com>
Subject: [linux-next:master 6443/6992] mm/huge_memory.c:80:24: warning: 'huge_anon_orders_lock' defined but not used
Date: Mon, 11 Dec 2023 19:37:07 +0800 [thread overview]
Message-ID: <202312111916.YbsHxKPq-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: bbd220ce4e29ed55ab079007cff0b550895258eb
commit: b197f32bc3d3d9f60977f31ad3e9eadb2123ca60 [6443/6992] mm: thp: introduce multi-size THP sysfs interface
config: s390-randconfig-r006-20230501 (https://download.01.org/0day-ci/archive/20231211/202312111916.YbsHxKPq-lkp@intel.com/config)
compiler: s390-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231211/202312111916.YbsHxKPq-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202312111916.YbsHxKPq-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from include/linux/spinlock.h:89,
from include/linux/mmzone.h:8,
from include/linux/gfp.h:7,
from include/linux/mm.h:7,
from mm/huge_memory.c:8:
>> mm/huge_memory.c:80:24: warning: 'huge_anon_orders_lock' defined but not used [-Wunused-variable]
80 | static DEFINE_SPINLOCK(huge_anon_orders_lock);
| ^~~~~~~~~~~~~~~~~~~~~
include/linux/spinlock_types.h:43:44: note: in definition of macro 'DEFINE_SPINLOCK'
43 | #define DEFINE_SPINLOCK(x) spinlock_t x = __SPIN_LOCK_UNLOCKED(x)
| ^
vim +/huge_anon_orders_lock +80 mm/huge_memory.c
48
49 /*
50 * By default, transparent hugepage support is disabled in order to avoid
51 * risking an increased memory footprint for applications that are not
52 * guaranteed to benefit from it. When transparent hugepage support is
53 * enabled, it is for all mappings, and khugepaged scans all mappings.
54 * Defrag is invoked by khugepaged hugepage allocations and by page faults
55 * for all hugepage allocations.
56 */
57 unsigned long transparent_hugepage_flags __read_mostly =
58 #ifdef CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS
59 (1<<TRANSPARENT_HUGEPAGE_FLAG)|
60 #endif
61 #ifdef CONFIG_TRANSPARENT_HUGEPAGE_MADVISE
62 (1<<TRANSPARENT_HUGEPAGE_REQ_MADV_FLAG)|
63 #endif
64 (1<<TRANSPARENT_HUGEPAGE_DEFRAG_REQ_MADV_FLAG)|
65 (1<<TRANSPARENT_HUGEPAGE_DEFRAG_KHUGEPAGED_FLAG)|
66 (1<<TRANSPARENT_HUGEPAGE_USE_ZERO_PAGE_FLAG);
67
68 static struct shrinker *deferred_split_shrinker;
69 static unsigned long deferred_split_count(struct shrinker *shrink,
70 struct shrink_control *sc);
71 static unsigned long deferred_split_scan(struct shrinker *shrink,
72 struct shrink_control *sc);
73
74 static atomic_t huge_zero_refcount;
75 struct page *huge_zero_page __read_mostly;
76 unsigned long huge_zero_pfn __read_mostly = ~0UL;
77 unsigned long huge_anon_orders_always __read_mostly;
78 unsigned long huge_anon_orders_madvise __read_mostly;
79 unsigned long huge_anon_orders_inherit __read_mostly;
> 80 static DEFINE_SPINLOCK(huge_anon_orders_lock);
81
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2023-12-11 11:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 11:37 kernel test robot [this message]
2023-12-11 12:53 ` [PATCH] mm: thp: Fix build warning when CONFIG_SYSFS is disabled Ryan Roberts
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=202312111916.YbsHxKPq-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=ryan.roberts@arm.com \
--cc=v-songbaohua@oppo.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