All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Shakeel Butt <shakeel.butt@linux.dev>
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>,
	Roman Gushchin <roman.gushchin@linux.dev>,
	"T.J. Mercier" <tjmercier@google.com>
Subject: mm/workingset.c:621 workingset_update_node() warn: unsigned '_x' is never less than zero.
Date: Sun, 16 Feb 2025 03:56:06 +0800	[thread overview]
Message-ID: <202502160323.ZLUfooA0-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head:   7ff71e6d923969d933e1ba7e0db857782d36cd19
commit: 4715c6a753dccd15fd3a8928168f57e349205bd4 mm: cleanup WORKINGSET_NODES in workingset
date:   9 months ago
config: riscv-randconfig-r073-20250213 (https://download.01.org/0day-ci/archive/20250216/202502160323.ZLUfooA0-lkp@intel.com/config)
compiler: riscv32-linux-gcc (GCC) 14.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/202502160323.ZLUfooA0-lkp@intel.com/

New smatch warnings:
mm/workingset.c:621 workingset_update_node() warn: unsigned '_x' is never less than zero.
mm/workingset.c:746 shadow_lru_isolate() warn: unsigned '_x' is never less than zero.

Old smatch warnings:
include/linux/mm.h:1306 virt_to_head_page() warn: unsigned '_x' is never less than zero.

vim +/_x +621 mm/workingset.c

   617	
   618	void workingset_update_node(struct xa_node *node)
   619	{
   620		struct address_space *mapping;
 > 621		struct page *page = virt_to_page(node);
   622	
   623		/*
   624		 * Track non-empty nodes that contain only shadow entries;
   625		 * unlink those that contain pages or are being freed.
   626		 *
   627		 * Avoid acquiring the list_lru lock when the nodes are
   628		 * already where they should be. The list_empty() test is safe
   629		 * as node->private_list is protected by the i_pages lock.
   630		 */
   631		mapping = container_of(node->array, struct address_space, i_pages);
   632		lockdep_assert_held(&mapping->i_pages.xa_lock);
   633	
   634		if (node->count && node->count == node->nr_values) {
   635			if (list_empty(&node->private_list)) {
   636				list_lru_add_obj(&shadow_nodes, &node->private_list);
   637				__inc_node_page_state(page, WORKINGSET_NODES);
   638			}
   639		} else {
   640			if (!list_empty(&node->private_list)) {
   641				list_lru_del_obj(&shadow_nodes, &node->private_list);
   642				__dec_node_page_state(page, WORKINGSET_NODES);
   643			}
   644		}
   645	}
   646	
   647	static unsigned long count_shadow_nodes(struct shrinker *shrinker,
   648						struct shrink_control *sc)
   649	{
   650		unsigned long max_nodes;
   651		unsigned long nodes;
   652		unsigned long pages;
   653	
   654		nodes = list_lru_shrink_count(&shadow_nodes, sc);
   655		if (!nodes)
   656			return SHRINK_EMPTY;
   657	
   658		/*
   659		 * Approximate a reasonable limit for the nodes
   660		 * containing shadow entries. We don't need to keep more
   661		 * shadow entries than possible pages on the active list,
   662		 * since refault distances bigger than that are dismissed.
   663		 *
   664		 * The size of the active list converges toward 100% of
   665		 * overall page cache as memory grows, with only a tiny
   666		 * inactive list. Assume the total cache size for that.
   667		 *
   668		 * Nodes might be sparsely populated, with only one shadow
   669		 * entry in the extreme case. Obviously, we cannot keep one
   670		 * node for every eligible shadow entry, so compromise on a
   671		 * worst-case density of 1/8th. Below that, not all eligible
   672		 * refaults can be detected anymore.
   673		 *
   674		 * On 64-bit with 7 xa_nodes per page and 64 slots
   675		 * each, this will reclaim shadow entries when they consume
   676		 * ~1.8% of available memory:
   677		 *
   678		 * PAGE_SIZE / xa_nodes / node_entries * 8 / PAGE_SIZE
   679		 */
   680	#ifdef CONFIG_MEMCG
   681		if (sc->memcg) {
   682			struct lruvec *lruvec;
   683			int i;
   684	
   685			mem_cgroup_flush_stats_ratelimited(sc->memcg);
   686			lruvec = mem_cgroup_lruvec(sc->memcg, NODE_DATA(sc->nid));
   687			for (pages = 0, i = 0; i < NR_LRU_LISTS; i++)
   688				pages += lruvec_page_state_local(lruvec,
   689								 NR_LRU_BASE + i);
   690			pages += lruvec_page_state_local(
   691				lruvec, NR_SLAB_RECLAIMABLE_B) >> PAGE_SHIFT;
   692			pages += lruvec_page_state_local(
   693				lruvec, NR_SLAB_UNRECLAIMABLE_B) >> PAGE_SHIFT;
   694		} else
   695	#endif
   696			pages = node_present_pages(sc->nid);
   697	
   698		max_nodes = pages >> (XA_CHUNK_SHIFT - 3);
   699	
   700		if (nodes <= max_nodes)
   701			return 0;
   702		return nodes - max_nodes;
   703	}
   704	
   705	static enum lru_status shadow_lru_isolate(struct list_head *item,
   706						  struct list_lru_one *lru,
   707						  spinlock_t *lru_lock,
   708						  void *arg) __must_hold(lru_lock)
   709	{
   710		struct xa_node *node = container_of(item, struct xa_node, private_list);
   711		struct address_space *mapping;
   712		int ret;
   713	
   714		/*
   715		 * Page cache insertions and deletions synchronously maintain
   716		 * the shadow node LRU under the i_pages lock and the
   717		 * lru_lock.  Because the page cache tree is emptied before
   718		 * the inode can be destroyed, holding the lru_lock pins any
   719		 * address_space that has nodes on the LRU.
   720		 *
   721		 * We can then safely transition to the i_pages lock to
   722		 * pin only the address_space of the particular node we want
   723		 * to reclaim, take the node off-LRU, and drop the lru_lock.
   724		 */
   725	
   726		mapping = container_of(node->array, struct address_space, i_pages);
   727	
   728		/* Coming from the list, invert the lock order */
   729		if (!xa_trylock(&mapping->i_pages)) {
   730			spin_unlock_irq(lru_lock);
   731			ret = LRU_RETRY;
   732			goto out;
   733		}
   734	
   735		/* For page cache we need to hold i_lock */
   736		if (mapping->host != NULL) {
   737			if (!spin_trylock(&mapping->host->i_lock)) {
   738				xa_unlock(&mapping->i_pages);
   739				spin_unlock_irq(lru_lock);
   740				ret = LRU_RETRY;
   741				goto out;
   742			}
   743		}
   744	
   745		list_lru_isolate(lru, item);
 > 746		__dec_node_page_state(virt_to_page(node), WORKINGSET_NODES);
   747	
   748		spin_unlock(lru_lock);
   749	
   750		/*
   751		 * The nodes should only contain one or more shadow entries,
   752		 * no pages, so we expect to be able to remove them all and
   753		 * delete and free the empty node afterwards.
   754		 */
   755		if (WARN_ON_ONCE(!node->nr_values))
   756			goto out_invalid;
   757		if (WARN_ON_ONCE(node->count != node->nr_values))
   758			goto out_invalid;
   759		xa_delete_node(node, workingset_update_node);
   760		__inc_lruvec_kmem_state(node, WORKINGSET_NODERECLAIM);
   761	
   762	out_invalid:
   763		xa_unlock_irq(&mapping->i_pages);
   764		if (mapping->host != NULL) {
   765			if (mapping_shrinkable(mapping))
   766				inode_add_lru(mapping->host);
   767			spin_unlock(&mapping->host->i_lock);
   768		}
   769		ret = LRU_REMOVED_RETRY;
   770	out:
   771		cond_resched();
   772		spin_lock_irq(lru_lock);
   773		return ret;
   774	}
   775	

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

             reply	other threads:[~2025-02-15 19:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-15 19:56 kernel test robot [this message]
2025-02-18  4:21 ` mm/workingset.c:621 workingset_update_node() warn: unsigned '_x' is never less than zero Andrew Morton
2025-02-18  4:21   ` Andrew Morton
2025-02-18  4:55   ` Alexandre Ghiti
2025-02-18  4:55     ` Alexandre Ghiti

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=202502160323.ZLUfooA0-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=roman.gushchin@linux.dev \
    --cc=shakeel.butt@linux.dev \
    --cc=tjmercier@google.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 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.