All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com,
	Guenter Roeck <groeck@google.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [chrome-os:chromeos-5.15 8/9] kernel/sched/deadline.c:1543:6: sparse: sparse: symbol 'dl_server_freeze' was not declared. Should it be static?
Date: Sun, 12 May 2024 09:29:13 +0800	[thread overview]
Message-ID: <202405120932.H7VBwEt2-lkp@intel.com> (raw)

tree:   https://chromium.googlesource.com/chromiumos/third_party/kernel chromeos-5.15
head:   a9b51c2494133c012e34a050191e3954b5109747
commit: 16d0ae5e68d0f8b9e3749021fd3599d88b72fc6c [8/9] CHROMIUM: sched/dlserver: Freeze dlserver on system suspend.
config: x86_64-randconfig-121-20240512 (https://download.01.org/0day-ci/archive/20240512/202405120932.H7VBwEt2-lkp@intel.com/config)
compiler: gcc-12 (Ubuntu 12.3.0-9ubuntu2) 12.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240512/202405120932.H7VBwEt2-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/202405120932.H7VBwEt2-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
   kernel/sched/deadline.c:2171:42: sparse: sparse: incorrect type in argument 2 (different address spaces) @@     expected struct sched_dl_entity *b @@     got struct sched_dl_entity [noderef] __rcu * @@
   kernel/sched/deadline.c:2171:42: sparse:     expected struct sched_dl_entity *b
   kernel/sched/deadline.c:2171:42: sparse:     got struct sched_dl_entity [noderef] __rcu *
   kernel/sched/deadline.c:1238:23: sparse: sparse: incorrect type in argument 1 (different address spaces) @@     expected struct task_struct *p @@     got struct task_struct [noderef] __rcu *curr @@
   kernel/sched/deadline.c:1238:23: sparse:     expected struct task_struct *p
   kernel/sched/deadline.c:1238:23: sparse:     got struct task_struct [noderef] __rcu *curr
>> kernel/sched/deadline.c:1543:6: sparse: sparse: symbol 'dl_server_freeze' was not declared. Should it be static?
>> kernel/sched/deadline.c:1552:6: sparse: sparse: symbol 'dl_server_thaw' was not declared. Should it be static?
   kernel/sched/deadline.c:1656:38: sparse: sparse: incorrect type in initializer (different address spaces) @@     expected struct task_struct *curr @@     got struct task_struct [noderef] __rcu *curr @@
   kernel/sched/deadline.c:1656:38: sparse:     expected struct task_struct *curr
   kernel/sched/deadline.c:1656:38: sparse:     got struct task_struct [noderef] __rcu *curr
   kernel/sched/deadline.c:2906:22: sparse: sparse: incompatible types in comparison expression (different address spaces):
   kernel/sched/deadline.c:2906:22: sparse:    struct task_struct [noderef] __rcu *
   kernel/sched/deadline.c:2906:22: sparse:    struct task_struct *
   kernel/sched/deadline.c:1140:29: sparse: sparse: context imbalance in 'dl_task_timer' - different lock contexts for basic block
   kernel/sched/deadline.c:1394:36: sparse: sparse: dereference of noderef expression
   kernel/sched/deadline.c: note: in included file:
   kernel/sched/sched.h:1605:9: sparse: sparse: context imbalance in 'inactive_task_timer' - unexpected unlock
   kernel/sched/sched.h:2076:25: sparse: sparse: incompatible types in comparison expression (different address spaces):
   kernel/sched/sched.h:2076:25: sparse:    struct task_struct [noderef] __rcu *
   kernel/sched/sched.h:2076:25: sparse:    struct task_struct *
   kernel/sched/sched.h:2076:25: sparse: sparse: incompatible types in comparison expression (different address spaces):
   kernel/sched/sched.h:2076:25: sparse:    struct task_struct [noderef] __rcu *
   kernel/sched/sched.h:2076:25: sparse:    struct task_struct *

vim +/dl_server_freeze +1543 kernel/sched/deadline.c

  1542	
> 1543	void dl_server_freeze(struct sched_dl_entity *dl_se)
  1544	{
  1545		if (dl_se->dl_server_active) {
  1546			update_rq_clock(dl_se->rq);
  1547			__dl_server_stop(dl_se);
  1548		}
  1549		dl_se->dl_server_frozen = 1;
  1550	}
  1551	
> 1552	void dl_server_thaw(struct sched_dl_entity *dl_se)
  1553	{
  1554		if (dl_se->dl_server_active) {
  1555			update_rq_clock(dl_se->rq);
  1556			__dl_server_start(dl_se);
  1557		}
  1558		dl_se->dl_server_frozen = 0;
  1559	}
  1560	

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

                 reply	other threads:[~2024-05-12  1:29 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202405120932.H7VBwEt2-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=cros-kernel-buildreports@googlegroups.com \
    --cc=groeck@google.com \
    --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 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.