linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Kairui Song <kasong@tencent.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>
Subject: mm/list_lru.c:514:3-8: WARNING: NULL check before some freeing functions is not needed.
Date: Sun, 29 Dec 2024 09:59:48 +0800	[thread overview]
Message-ID: <202412290924.UTP7GH2Z-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head:   059dd502b263d8a4e2a84809cf1068d6a3905e6f
commit: 28e98022b31efdb8f1ba310d938cd9b97ededfe4 mm/list_lru: simplify reparenting and initial allocation
date:   7 weeks ago
config: i386-randconfig-054-20241229 (https://download.01.org/0day-ci/archive/20241229/202412290924.UTP7GH2Z-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.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/202412290924.UTP7GH2Z-lkp@intel.com/

cocci warnings: (new ones prefixed by >>)
>> mm/list_lru.c:514:3-8: WARNING: NULL check before some freeing functions is not needed.

vim +514 mm/list_lru.c

   470	
   471	int memcg_list_lru_alloc(struct mem_cgroup *memcg, struct list_lru *lru,
   472				 gfp_t gfp)
   473	{
   474		unsigned long flags;
   475		struct list_lru_memcg *mlru;
   476		struct mem_cgroup *pos, *parent;
   477		XA_STATE(xas, &lru->xa, 0);
   478	
   479		if (!list_lru_memcg_aware(lru) || memcg_list_lru_allocated(memcg, lru))
   480			return 0;
   481	
   482		gfp &= GFP_RECLAIM_MASK;
   483		/*
   484		 * Because the list_lru can be reparented to the parent cgroup's
   485		 * list_lru, we should make sure that this cgroup and all its
   486		 * ancestors have allocated list_lru_memcg.
   487		 */
   488		do {
   489			/*
   490			 * Keep finding the farest parent that wasn't populated
   491			 * until found memcg itself.
   492			 */
   493			pos = memcg;
   494			parent = parent_mem_cgroup(pos);
   495			while (!memcg_list_lru_allocated(parent, lru)) {
   496				pos = parent;
   497				parent = parent_mem_cgroup(pos);
   498			}
   499	
   500			mlru = memcg_init_list_lru_one(gfp);
   501			if (!mlru)
   502				return -ENOMEM;
   503			xas_set(&xas, pos->kmemcg_id);
   504			do {
   505				xas_lock_irqsave(&xas, flags);
   506				if (!xas_load(&xas) && !css_is_dying(&pos->css)) {
   507					xas_store(&xas, mlru);
   508					if (!xas_error(&xas))
   509						mlru = NULL;
   510				}
   511				xas_unlock_irqrestore(&xas, flags);
   512			} while (xas_nomem(&xas, gfp));
   513			if (mlru)
 > 514				kfree(mlru);
   515		} while (pos != memcg && !css_is_dying(&pos->css));
   516	
   517		return xas_error(&xas);
   518	}
   519	#else
   520	static inline void memcg_init_list_lru(struct list_lru *lru, bool memcg_aware)
   521	{
   522	}
   523	

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


             reply	other threads:[~2024-12-29  2:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-29  1:59 kernel test robot [this message]
2024-12-29  9:39 ` Kairui Song

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=202412290924.UTP7GH2Z-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=kasong@tencent.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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