From: Baolin Wang <baolin.wang@linux.alibaba.com>
To: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [linux-next:master 4839/5501] mm/shmem.c:139:24: warning: 'huge_shmem_orders_lock' defined but not used
Date: Sun, 16 Jun 2024 21:45:27 +0800 [thread overview]
Message-ID: <eb34da66-7f12-44f3-a39e-2bcc90c33354@linux.alibaba.com> (raw)
In-Reply-To: <202406152213.CoQNZR6z-lkp@intel.com>
On 2024/6/15 22:15, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: 6906a84c482f098d31486df8dc98cead21cce2d0
> commit: dfe69b2f4ed49aee4a46f09010f7888ee289083d [4839/5501] mm: shmem: add multi-size THP sysfs interface for anonymous shmem
> config: mips-randconfig-r034-20220430 (https://download.01.org/0day-ci/archive/20240615/202406152213.CoQNZR6z-lkp@intel.com/config)
> compiler: mips-linux-gcc (GCC) 13.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240615/202406152213.CoQNZR6z-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/202406152213.CoQNZR6z-lkp@intel.com/
>
> All warnings (new ones prefixed by >>):
>
> In file included from include/linux/spinlock.h:89,
> from include/linux/wait.h:9,
> from include/linux/wait_bit.h:8,
> from include/linux/fs.h:6,
> from mm/shmem.c:24:
>>> mm/shmem.c:139:24: warning: 'huge_shmem_orders_lock' defined but not used [-Wunused-variable]
> 139 | static DEFINE_SPINLOCK(huge_shmem_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)
> | ^
> mm/shmem.c:138:22: warning: 'huge_shmem_orders_within_size' defined but not used [-Wunused-variable]
> 138 | static unsigned long huge_shmem_orders_within_size __read_mostly;
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> mm/shmem.c:136:22: warning: 'huge_shmem_orders_madvise' defined but not used [-Wunused-variable]
> 136 | static unsigned long huge_shmem_orders_madvise __read_mostly;
> | ^~~~~~~~~~~~~~~~~~~~~~~~~
> mm/shmem.c:135:22: warning: 'huge_shmem_orders_always' defined but not used [-Wunused-variable]
> 135 | static unsigned long huge_shmem_orders_always __read_mostly;
> | ^~~~~~~~~~~~~~~~~~~~~~~~
>
>
> vim +/huge_shmem_orders_lock +139 mm/shmem.c
>
> 133
> 134 #ifdef CONFIG_TRANSPARENT_HUGEPAGE
> 135 static unsigned long huge_shmem_orders_always __read_mostly;
> 136 static unsigned long huge_shmem_orders_madvise __read_mostly;
> 137 static unsigned long huge_shmem_orders_inherit __read_mostly;
> 138 static unsigned long huge_shmem_orders_within_size __read_mostly;
> > 139 static DEFINE_SPINLOCK(huge_shmem_orders_lock);
> 140 #endif
> 141
Thanks for reporting. I should move the 'huge_shmem_orders_lock' under
CONFIG_SYSFS config.
@Andrew, please help to squash the following fix into this patch. Thanks.
diff --git a/mm/shmem.c b/mm/shmem.c
index 4acaf02bfe44..d09c6bf1f28a 100644
--- a/mm/shmem.c
+++ b/mm/shmem.c
@@ -136,7 +136,6 @@ static unsigned long huge_shmem_orders_always
__read_mostly;
static unsigned long huge_shmem_orders_madvise __read_mostly;
static unsigned long huge_shmem_orders_inherit __read_mostly;
static unsigned long huge_shmem_orders_within_size __read_mostly;
-static DEFINE_SPINLOCK(huge_shmem_orders_lock);
#endif
#ifdef CONFIG_TMPFS
@@ -4918,6 +4917,7 @@ static ssize_t shmem_enabled_store(struct kobject
*kobj,
}
struct kobj_attribute shmem_enabled_attr = __ATTR_RW(shmem_enabled);
+static DEFINE_SPINLOCK(huge_shmem_orders_lock);
static ssize_t thpsize_shmem_enabled_show(struct kobject *kobj,
struct kobj_attribute *attr,
char *buf)
prev parent reply other threads:[~2024-06-16 13:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-15 14:15 kernel test robot
2024-06-16 13:45 ` Baolin Wang [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=eb34da66-7f12-44f3-a39e-2bcc90c33354@linux.alibaba.com \
--to=baolin.wang@linux.alibaba.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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