From: kernel test robot <lkp@intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Subject: kernel/futex/core.c:1748:2-8: WARNING: NULL check before some freeing functions is not needed.
Date: Mon, 02 Feb 2026 10:05:00 +0800 [thread overview]
Message-ID: <202602021017.JuULzLgI-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 18f7fcd5e69a04df57b563360b88be72471d6b62
commit: 56180dd20c19e5b0fa34822997a9ac66b517e7b3 futex: Use RCU-based per-CPU reference counting instead of rcuref_t
date: 7 months ago
config: x86_64-randconfig-r061-20260201 (https://download.01.org/0day-ci/archive/20260202/202602021017.JuULzLgI-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
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/202602021017.JuULzLgI-lkp@intel.com/
cocci warnings: (new ones prefixed by >>)
>> kernel/futex/core.c:1748:2-8: WARNING: NULL check before some freeing functions is not needed.
vim +1748 kernel/futex/core.c
56180dd20c19e5 Peter Zijlstra 2025-07-10 1739
80367ad01d93ac Sebastian Andrzej Siewior 2025-04-16 1740 void futex_hash_free(struct mm_struct *mm)
80367ad01d93ac Sebastian Andrzej Siewior 2025-04-16 1741 {
bd54df5ea7cada Sebastian Andrzej Siewior 2025-04-16 1742 struct futex_private_hash *fph;
bd54df5ea7cada Sebastian Andrzej Siewior 2025-04-16 1743
56180dd20c19e5 Peter Zijlstra 2025-07-10 1744 free_percpu(mm->futex_ref);
bd54df5ea7cada Sebastian Andrzej Siewior 2025-04-16 1745 kvfree(mm->futex_phash_new);
bd54df5ea7cada Sebastian Andrzej Siewior 2025-04-16 1746 fph = rcu_dereference_raw(mm->futex_phash);
56180dd20c19e5 Peter Zijlstra 2025-07-10 1747 if (fph)
bd54df5ea7cada Sebastian Andrzej Siewior 2025-04-16 @1748 kvfree(fph);
bd54df5ea7cada Sebastian Andrzej Siewior 2025-04-16 1749 }
bd54df5ea7cada Sebastian Andrzej Siewior 2025-04-16 1750
:::::: The code at line 1748 was first introduced by commit
:::::: bd54df5ea7cadac520e346d5f0fe5d58e635b6ba futex: Allow to resize the private local hash
:::::: TO: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
:::::: CC: Peter Zijlstra <peterz@infradead.org>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-02-02 2:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-02 2:05 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-06-04 5:01 kernel/futex/core.c:1748:2-8: WARNING: NULL check before some freeing functions is not needed kernel test robot
2026-03-23 19:41 kernel test robot
2026-02-01 16:39 kernel test robot
2025-12-22 13:50 kernel test robot
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=202602021017.JuULzLgI-lkp@intel.com \
--to=lkp@intel.com \
--cc=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=peterz@infradead.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.