All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: "Jim Cromie" <jim.cromie@gmail.com>,
	"Łukasz Bartosik" <ukaszb@chromium.org>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [jimc:dd-shrink-4d 77/82] lib/dynamic_debug.c:1420:13: warning: 'ddebug_clear_range' defined but not used
Date: Wed, 30 Oct 2024 05:30:17 +0800	[thread overview]
Message-ID: <202410300507.PWcBsqXP-lkp@intel.com> (raw)

tree:   https://github.com/jimc/linux.git dd-shrink-4d
head:   98a15f4b1948cdaabac1f0fc008c79870c4d4672
commit: 258c09446f7441ccdbdeb1f9c32d97bd27064d25 [77/82] dyndbg: ddebug_clear_range - prune module's site info on rmmod
config: x86_64-buildonly-randconfig-003-20241030 (https://download.01.org/0day-ci/archive/20241030/202410300507.PWcBsqXP-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/20241030/202410300507.PWcBsqXP-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/202410300507.PWcBsqXP-lkp@intel.com/

All warnings (new ones prefixed by >>):

   lib/dynamic_debug.c: In function 'ddebug_mt_scan':
   lib/dynamic_debug.c:94:9: error: implicit declaration of function 'mt_dump'; did you mean 'xa_dump'? [-Werror=implicit-function-declaration]
      94 |         mt_dump(mt, mt_dump_hex);
         |         ^~~~~~~
         |         xa_dump
   lib/dynamic_debug.c:94:21: error: 'mt_dump_hex' undeclared (first use in this function)
      94 |         mt_dump(mt, mt_dump_hex);
         |                     ^~~~~~~~~~~
   lib/dynamic_debug.c:94:21: note: each undeclared identifier is reported only once for each function it appears in
   lib/dynamic_debug.c: At top level:
   lib/dynamic_debug.c:1480:12: warning: 'ddebug_remove_module' used but never defined
    1480 | static int ddebug_remove_module(const char *mod_name);
         |            ^~~~~~~~~~~~~~~~~~~~
>> lib/dynamic_debug.c:1420:13: warning: 'ddebug_clear_range' defined but not used [-Wunused-function]
    1420 | static void ddebug_clear_range(const struct _ddebug *_start, const int len)
         |             ^~~~~~~~~~~~~~~~~~
   cc1: some warnings being treated as errors


vim +/ddebug_clear_range +1420 lib/dynamic_debug.c

  1419	
> 1420	static void ddebug_clear_range(const struct _ddebug *_start, const int len)
  1421	{
  1422		void *ret;
  1423		unsigned long start = (unsigned long) _start;
  1424		MA_STATE(file_mas, &mt_files, start, start);
  1425		MA_STATE(func_mas, &mt_funcs, start, start);
  1426	
  1427		v2pr_info("clearing %3d debugs %px\n", len, _start);
  1428		ret = mtree_erase(&mt_mods, start);
  1429		v2pr_info("mods:  %px %s\n", ret, (char*)ret);
  1430	
  1431		mas_lock(&file_mas);
  1432		for (; mas_erase(&file_mas); file_mas.index = file_mas.last + 1)
  1433			;
  1434		mas_unlock(&file_mas);
  1435	
  1436		mas_lock(&func_mas);
  1437		for (; mas_erase(&func_mas); func_mas.index = func_mas.last + 1)
  1438			;
  1439		mas_unlock(&func_mas);
  1440	}
  1441	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2024-10-29 21:30 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=202410300507.PWcBsqXP-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=jim.cromie@gmail.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=ukaszb@chromium.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.