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
Subject: Re: [RFC PATCH 3/3] memcg-v1: remove memcg move locking code
Date: Sun, 27 Oct 2024 15:03:05 +0800	[thread overview]
Message-ID: <202410271408.tc8QGSge-lkp@intel.com> (raw)
In-Reply-To: <20241024065712.1274481-4-shakeel.butt@linux.dev>

Hi Shakeel,

[This is a private test report for your RFC patch.]
kernel test robot noticed the following build warnings:

[auto build test WARNING on akpm-mm/mm-everything]
[also build test WARNING on next-20241025]
[cannot apply to tj-cgroup/for-next brauner-vfs/vfs.all linus/master v6.12-rc4]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/Shakeel-Butt/memcg-v1-fully-deprecate-move_charge_at_immigrate/20241025-132623
base:   https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-everything
patch link:    https://lore.kernel.org/r/20241024065712.1274481-4-shakeel.butt%40linux.dev
patch subject: [RFC PATCH 3/3] memcg-v1: remove memcg move locking code
config: arc-randconfig-002-20241027 (https://download.01.org/0day-ci/archive/20241027/202410271408.tc8QGSge-lkp@intel.com/config)
compiler: arceb-elf-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241027/202410271408.tc8QGSge-lkp@intel.com/reproduce)

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/202410271408.tc8QGSge-lkp@intel.com/

All warnings (new ones prefixed by >>):

   mm/vmscan.c: In function 'walk_mm':
>> mm/vmscan.c:3652:28: warning: unused variable 'memcg' [-Wunused-variable]
    3652 |         struct mem_cgroup *memcg = lruvec_memcg(lruvec);
         |                            ^~~~~


vim +/memcg +3652 mm/vmscan.c

bd74fdaea14602 Yu Zhao            2022-09-18  3641  
2d823764fafa65 Kinsey Ho          2024-02-14  3642  static void walk_mm(struct mm_struct *mm, struct lru_gen_mm_walk *walk)
bd74fdaea14602 Yu Zhao            2022-09-18  3643  {
bd74fdaea14602 Yu Zhao            2022-09-18  3644  	static const struct mm_walk_ops mm_walk_ops = {
bd74fdaea14602 Yu Zhao            2022-09-18  3645  		.test_walk = should_skip_vma,
bd74fdaea14602 Yu Zhao            2022-09-18  3646  		.p4d_entry = walk_pud_range,
49b0638502da09 Suren Baghdasaryan 2023-08-04  3647  		.walk_lock = PGWALK_RDLOCK,
bd74fdaea14602 Yu Zhao            2022-09-18  3648  	};
bd74fdaea14602 Yu Zhao            2022-09-18  3649  
bd74fdaea14602 Yu Zhao            2022-09-18  3650  	int err;
2d823764fafa65 Kinsey Ho          2024-02-14  3651  	struct lruvec *lruvec = walk->lruvec;
bd74fdaea14602 Yu Zhao            2022-09-18 @3652  	struct mem_cgroup *memcg = lruvec_memcg(lruvec);
bd74fdaea14602 Yu Zhao            2022-09-18  3653  
bd74fdaea14602 Yu Zhao            2022-09-18  3654  	walk->next_addr = FIRST_USER_ADDRESS;
bd74fdaea14602 Yu Zhao            2022-09-18  3655  
bd74fdaea14602 Yu Zhao            2022-09-18  3656  	do {
7f63cf2d9b9bbe Kalesh Singh       2023-04-13  3657  		DEFINE_MAX_SEQ(lruvec);
7f63cf2d9b9bbe Kalesh Singh       2023-04-13  3658  
bd74fdaea14602 Yu Zhao            2022-09-18  3659  		err = -EBUSY;
bd74fdaea14602 Yu Zhao            2022-09-18  3660  
7f63cf2d9b9bbe Kalesh Singh       2023-04-13  3661  		/* another thread might have called inc_max_seq() */
cc25bbe10a86a7 Kinsey Ho          2024-02-14  3662  		if (walk->seq != max_seq)
7f63cf2d9b9bbe Kalesh Singh       2023-04-13  3663  			break;
7f63cf2d9b9bbe Kalesh Singh       2023-04-13  3664  
bd74fdaea14602 Yu Zhao            2022-09-18  3665  		/* the caller might be holding the lock for write */
bd74fdaea14602 Yu Zhao            2022-09-18  3666  		if (mmap_read_trylock(mm)) {
bd74fdaea14602 Yu Zhao            2022-09-18  3667  			err = walk_page_range(mm, walk->next_addr, ULONG_MAX, &mm_walk_ops, walk);
bd74fdaea14602 Yu Zhao            2022-09-18  3668  
bd74fdaea14602 Yu Zhao            2022-09-18  3669  			mmap_read_unlock(mm);
bd74fdaea14602 Yu Zhao            2022-09-18  3670  		}
bd74fdaea14602 Yu Zhao            2022-09-18  3671  
bd74fdaea14602 Yu Zhao            2022-09-18  3672  		if (walk->batched) {
bd74fdaea14602 Yu Zhao            2022-09-18  3673  			spin_lock_irq(&lruvec->lru_lock);
2d823764fafa65 Kinsey Ho          2024-02-14  3674  			reset_batch_size(walk);
bd74fdaea14602 Yu Zhao            2022-09-18  3675  			spin_unlock_irq(&lruvec->lru_lock);
bd74fdaea14602 Yu Zhao            2022-09-18  3676  		}
bd74fdaea14602 Yu Zhao            2022-09-18  3677  
bd74fdaea14602 Yu Zhao            2022-09-18  3678  		cond_resched();
bd74fdaea14602 Yu Zhao            2022-09-18  3679  	} while (err == -EAGAIN);
bd74fdaea14602 Yu Zhao            2022-09-18  3680  }
bd74fdaea14602 Yu Zhao            2022-09-18  3681  

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

  parent reply	other threads:[~2024-10-27  7:03 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-24  6:57 [RFC PATCH 0/3] memcg-v1: fully deprecate charge moving Shakeel Butt
2024-10-24  6:57 ` [RFC PATCH 1/3] memcg-v1: fully deprecate move_charge_at_immigrate Shakeel Butt
2024-10-24  9:14   ` Michal Hocko
2024-10-24 16:51     ` Roman Gushchin
2024-10-24 17:16       ` Shakeel Butt
2024-10-24 16:49   ` Roman Gushchin
2024-10-24  6:57 ` [RFC PATCH 2/3] memcg-v1: remove charge move code Shakeel Butt
2024-10-24  9:14   ` Michal Hocko
2024-10-24 16:50   ` Roman Gushchin
2024-10-24  6:57 ` [RFC PATCH 3/3] memcg-v1: remove memcg move locking code Shakeel Butt
2024-10-25  1:23   ` Shakeel Butt
2024-10-24  9:16   ` Michal Hocko
2024-10-24 17:23     ` Shakeel Butt
2024-10-24 18:54       ` Roman Gushchin
2024-10-24 19:38         ` Shakeel Butt
2024-10-24 16:50   ` Roman Gushchin
2024-10-24 17:26     ` Shakeel Butt
2024-10-24 19:45       ` Michal Hocko
2024-10-24 20:32         ` Yosry Ahmed
2024-10-24 21:08           ` Michal Hocko
2024-10-27  7:03   ` kernel test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-10-25  1:22 [PATCH v1 0/6] memcg-v1: fully deprecate charge moving Shakeel Butt
2024-10-25  1:22 ` [PATCH v1 1/6] memcg-v1: fully deprecate move_charge_at_immigrate Shakeel Butt
2024-10-25  6:54   ` Michal Hocko
2024-10-28 13:53   ` Johannes Weiner
2024-10-25  1:22 ` [PATCH v1 2/6] memcg-v1: remove charge move code Shakeel Butt
2024-10-28 10:22   ` David Hildenbrand
2024-10-28 10:40     ` David Hildenbrand
2024-10-28 13:54   ` Johannes Weiner
2024-10-25  1:23 ` [PATCH v1 3/6] memcg-v1: no need for memcg locking for dirty tracking Shakeel Butt
2024-10-25  6:56   ` Michal Hocko
2024-10-25 16:22     ` Shakeel Butt
2024-10-25 17:40   ` Roman Gushchin
2024-10-28 14:00   ` Johannes Weiner
2024-10-25  1:23 ` [PATCH v1 4/6] memcg-v1: no need for memcg locking for writeback tracking Shakeel Butt
2024-10-25  6:57   ` Michal Hocko
2024-10-25 17:40   ` Roman Gushchin
2024-10-28 14:00   ` Johannes Weiner
2024-10-25  1:23 ` [PATCH v1 5/6] memcg-v1: no need for memcg locking for MGLRU Shakeel Butt
2024-10-25 17:41   ` Roman Gushchin
2024-10-26  3:55   ` Yu Zhao
2024-10-26  6:20     ` Shakeel Butt
2024-10-26  6:34   ` Shakeel Butt
2024-10-26 15:26     ` Yu Zhao
2024-11-04 17:30       ` Yu Zhao
2024-11-04 21:38         ` Andrew Morton
2024-11-04 22:04           ` Shakeel Butt
2024-11-04 22:04           ` Yu Zhao
2024-11-04 22:08             ` Yu Zhao
2024-11-04 22:18               ` Andrew Morton
2024-10-25  1:23 ` [PATCH v1 6/6] memcg-v1: remove memcg move locking code Shakeel Butt
2024-10-25  6:59   ` Michal Hocko
2024-10-25 17:42   ` Roman Gushchin
2024-10-26  3:58   ` Yu Zhao
2024-10-26  6:26     ` Shakeel Butt
2024-10-28 14:02   ` Johannes Weiner
2024-10-25  1:33 ` [PATCH v1 0/6] memcg-v1: fully deprecate charge moving Shakeel Butt

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=202410271408.tc8QGSge-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=shakeel.butt@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 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.