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-ratelimit-2 61/76] lib/dynamic_debug_ratelimit.c:151:4-9: WARNING: NULL check before some freeing functions is not needed.
Date: Wed, 19 Aug 2026 23:54:36 +0800 [thread overview]
Message-ID: <202608192319.yPitUgGb-lkp@intel.com> (raw)
tree: https://github.com/jimc/linux.git dd-ratelimit-2
head: 31212444bcca4d1547711ec572b5a398d74640ca
commit: 3ffeebe328d9f1bc581ba7163321a9519ec821d3 [61/76] lib/dynamic_debug: Implement dynamic solo and shared rate-limiting
config: nios2-randconfig-r051-20260819 (https://download.01.org/0day-ci/archive/20260819/202608192319.yPitUgGb-lkp@intel.com/config)
compiler: nios2-linux-gcc (GCC) 11.5.0
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/202608192319.yPitUgGb-lkp@intel.com/
cocci warnings: (new ones prefixed by >>)
>> lib/dynamic_debug_ratelimit.c:151:4-9: WARNING: NULL check before some freeing functions is not needed.
vim +151 lib/dynamic_debug_ratelimit.c
140
141 void ddebug_ratelimit_free_info(const struct _ddebug_info *di)
142 {
143 int i;
144 struct _ddebug *dp;
145
146 for (i = 0; i < di->descs.len; i++) {
147 dp = &di->descs.start[i];
148 if (dp->flags & _DPRINTK_FLAGS_RATELIMIT_SOLO) {
149 struct ddebug_ratelimit_solo *wrapper = mtree_erase(&dd_ratelimits_solo, (unsigned long)dp);
150 if (wrapper)
> 151 kfree(wrapper); /* Unloading module context is safe for direct kfree */
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-08-19 15:55 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=202608192319.yPitUgGb-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.