From: kernel test robot <lkp@intel.com>
To: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 10764/11415] samples/hung_task/hung_task_mutex.c:25:15: sparse: sparse: symbol 'hung_task_dir' was not declared. Should it be static?
Date: Tue, 18 Mar 2025 08:31:21 +0800 [thread overview]
Message-ID: <202503180827.4StpuFrD-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: e94bd4ec45ac156616da285a0bf03056cd7430fc
commit: fb01916e3b56de4c9c6510202b446365082bdd3c [10764/11415] samples: add hung_task detector mutex blocking sample
config: i386-randconfig-r111-20250318 (https://download.01.org/0day-ci/archive/20250318/202503180827.4StpuFrD-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250318/202503180827.4StpuFrD-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/202503180827.4StpuFrD-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> samples/hung_task/hung_task_mutex.c:25:15: sparse: sparse: symbol 'hung_task_dir' was not declared. Should it be static?
vim +/hung_task_dir +25 samples/hung_task/hung_task_mutex.c
22
23 static const char dummy_string[] = "This is a dummy string.";
24 static DEFINE_MUTEX(dummy_mutex);
> 25 struct dentry *hung_task_dir;
26
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-03-18 0:32 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=202503180827.4StpuFrD-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=mhiramat@kernel.org \
--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