[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <202512241804.JAJl5a7k-lkp@intel.com>
Date: Wed, 24 Dec 2025 19:03:07 +0800
From: kernel test robot <lkp@...el.com>
To: Pavel Tikhomirov <ptikhomirov@...tuozzo.com>, Tejun Heo <tj@...nel.org>
Cc: oe-kbuild-all@...ts.linux.dev, Johannes Weiner <hannes@...xchg.org>,
Michal Koutný <mkoutny@...e.com>,
cgroups@...r.kernel.org, linux-kernel@...r.kernel.org,
Pavel Tikhomirov <ptikhomirov@...tuozzo.com>
Subject: Re: [PATCH 2/2] cgroup-v2/freezer: Print information about
unfreezable process
Hi Pavel,
kernel test robot noticed the following build warnings:
[auto build test WARNING on tj-cgroup/for-next]
[also build test WARNING on linus/master v6.19-rc2 next-20251219]
[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/Pavel-Tikhomirov/cgroup-v2-freezer-allow-freezing-with-kthreads/20251223-182826
base: https://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup.git for-next
patch link: https://lore.kernel.org/r/20251223102124.738818-4-ptikhomirov%40virtuozzo.com
patch subject: [PATCH 2/2] cgroup-v2/freezer: Print information about unfreezable process
config: arm64-randconfig-r134-20251224 (https://download.01.org/0day-ci/archive/20251224/202512241804.JAJl5a7k-lkp@intel.com/config)
compiler: clang version 22.0.0git (https://github.com/llvm/llvm-project 4ef602d446057dabf5f61fb221669ecbeda49279)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251224/202512241804.JAJl5a7k-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@...el.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202512241804.JAJl5a7k-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
kernel/cgroup/freezer.c:144:35: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct spinlock [usertype] *lock @@ got struct spinlock [noderef] __rcu * @@
kernel/cgroup/freezer.c:144:35: sparse: expected struct spinlock [usertype] *lock
kernel/cgroup/freezer.c:144:35: sparse: got struct spinlock [noderef] __rcu *
kernel/cgroup/freezer.c:147:37: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct spinlock [usertype] *lock @@ got struct spinlock [noderef] __rcu * @@
kernel/cgroup/freezer.c:147:37: sparse: expected struct spinlock [usertype] *lock
kernel/cgroup/freezer.c:147:37: sparse: got struct spinlock [noderef] __rcu *
>> kernel/cgroup/freezer.c:416:5: sparse: sparse: symbol 'sysctl_freeze_timeout_us' was not declared. Should it be static?
kernel/cgroup/freezer.c: note: in included file (through include/linux/rcuwait.h, include/linux/percpu-rwsem.h, include/linux/fs/super_types.h, ...):
include/linux/sched/signal.h:756:37: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct spinlock [usertype] *lock @@ got struct spinlock [noderef] __rcu * @@
include/linux/sched/signal.h:756:37: sparse: expected struct spinlock [usertype] *lock
include/linux/sched/signal.h:756:37: sparse: got struct spinlock [noderef] __rcu *
vim +/sysctl_freeze_timeout_us +416 kernel/cgroup/freezer.c
414
415 #define DEFAULT_FREEZE_RATELIMIT (30 * HZ)
> 416 int sysctl_freeze_timeout_us;
417
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Powered by blists - more mailing lists