From: kernel test robot <lkp@intel.com>
To: Joshua Hahn <joshua.hahnjy@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>,
Gregory Price <gourry@gourry.net>,
Harry Yoo <harry.yoo@oracle.com>,
Huang Ying <ying.huang@linux.alibaba.com>,
Honggyu Kim <honggyu.kim@sk.com>
Subject: mm/mempolicy.c:3719:1-6: ERROR: invalid free of structure field
Date: Sun, 1 Jun 2025 13:34:46 +0800 [thread overview]
Message-ID: <202506011545.Fduxqxqj-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 7d4e49a77d9930c69751b9192448fda6ff9100f1
commit: e341f9c3c8412e57fe0042a33a2640245ecdf619 mm/mempolicy: Weighted Interleave Auto-tuning
date: 11 days ago
config: loongarch-randconfig-r054-20250601 (https://download.01.org/0day-ci/archive/20250601/202506011545.Fduxqxqj-lkp@intel.com/config)
compiler: loongarch64-linux-gcc (GCC) 15.1.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/202506011545.Fduxqxqj-lkp@intel.com/
cocci warnings: (new ones prefixed by >>)
>> mm/mempolicy.c:3719:1-6: ERROR: invalid free of structure field
vim +3719 mm/mempolicy.c
3700
3701 static void wi_state_free(void)
3702 {
3703 struct weighted_interleave_state *old_wi_state;
3704
3705 mutex_lock(&wi_state_lock);
3706
3707 old_wi_state = rcu_dereference_protected(wi_state,
3708 lockdep_is_held(&wi_state_lock));
3709 if (!old_wi_state) {
3710 mutex_unlock(&wi_state_lock);
3711 goto out;
3712 }
3713
3714 rcu_assign_pointer(wi_state, NULL);
3715 mutex_unlock(&wi_state_lock);
3716 synchronize_rcu();
3717 kfree(old_wi_state);
3718 out:
> 3719 kfree(&wi_group->wi_kobj);
3720 }
3721
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2025-06-01 5:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-01 5:34 kernel test robot [this message]
2025-06-02 6:01 ` mm/mempolicy.c:3719:1-6: ERROR: invalid free of structure field Harry Yoo
2025-06-02 14:52 ` Joshua Hahn
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=202506011545.Fduxqxqj-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=gourry@gourry.net \
--cc=harry.yoo@oracle.com \
--cc=honggyu.kim@sk.com \
--cc=joshua.hahnjy@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=ying.huang@linux.alibaba.com \
/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