mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: "zhaoxiu.zeng" <zhaoxiu.zeng@gmail.com>,
	mingo@redhat.com, peterz@infradead.org, juri.lelli@redhat.com,
	vincent.guittot@linaro.org
Cc: kbuild-all@lists.01.org, dietmar.eggemann@arm.com,
	rostedt@goodmis.org, bsegall@google.com, mgorman@suse.de,
	bristot@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] schedule: SCHED_RR: Give a fresh time-slice to the task after after it suspends or relinquishes
Date: Thu, 23 Dec 2021 02:41:07 +0800	[thread overview]
Message-ID: <202112230234.B6uAyy2x-lkp@intel.com> (raw)
In-Reply-To: <20211222091526.8511-1-zhaoxiu.zeng@gmail.com>

Hi "zhaoxiu.zeng",

Thank you for the patch! Perhaps something to improve:

[auto build test WARNING on tip/sched/core]
[also build test WARNING on v5.16-rc6 next-20211222]
[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]

url:    https://github.com/0day-ci/linux/commits/zhaoxiu-zeng/schedule-SCHED_RR-Give-a-fresh-time-slice-to-the-task-after-after-it-suspends-or-relinquishes/20211222-171838
base:   https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git 82762d2af31a60081162890983a83499c9c7dd74
config: i386-randconfig-s001-20211222 (https://download.01.org/0day-ci/archive/20211223/202112230234.B6uAyy2x-lkp@intel.com/config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce:
        # apt-get install sparse
        # sparse version: v0.6.4-dirty
        # https://github.com/0day-ci/linux/commit/7e5fd85c65d2efc13de4adaa5ebc522894f3d60c
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review zhaoxiu-zeng/schedule-SCHED_RR-Give-a-fresh-time-slice-to-the-task-after-after-it-suspends-or-relinquishes/20211222-171838
        git checkout 7e5fd85c65d2efc13de4adaa5ebc522894f3d60c
        # save the config file to linux build tree
        mkdir build_dir
        make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=i386 SHELL=/bin/bash kernel/sched/

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>


sparse warnings: (new ones prefixed by >>)
   kernel/sched/rt.c:924:70: sparse: sparse: incompatible types in comparison expression (different address spaces):
   kernel/sched/rt.c:924:70: sparse:    struct task_struct [noderef] __rcu *
   kernel/sched/rt.c:924:70: sparse:    struct task_struct *
   kernel/sched/rt.c:1010:38: sparse: sparse: incorrect type in initializer (different address spaces) @@     expected struct task_struct *curr @@     got struct task_struct [noderef] __rcu *curr @@
   kernel/sched/rt.c:1010:38: sparse:     expected struct task_struct *curr
   kernel/sched/rt.c:1010:38: sparse:     got struct task_struct [noderef] __rcu *curr
>> kernel/sched/rt.c:1560:35: sparse: sparse: incorrect type in initializer (different address spaces) @@     expected struct task_struct *p @@     got struct task_struct [noderef] __rcu *curr @@
   kernel/sched/rt.c:1560:35: sparse:     expected struct task_struct *p
   kernel/sched/rt.c:1560:35: sparse:     got struct task_struct [noderef] __rcu *curr
   kernel/sched/rt.c: note: in included file:
   kernel/sched/sched.h:2032:25: sparse: sparse: incompatible types in comparison expression (different address spaces):
   kernel/sched/sched.h:2032:25: sparse:    struct task_struct [noderef] __rcu *
   kernel/sched/sched.h:2032:25: sparse:    struct task_struct *
   kernel/sched/sched.h:2032:25: sparse: sparse: incompatible types in comparison expression (different address spaces):
   kernel/sched/sched.h:2032:25: sparse:    struct task_struct [noderef] __rcu *
   kernel/sched/sched.h:2032:25: sparse:    struct task_struct *
   kernel/sched/sched.h:2032:25: sparse: sparse: incompatible types in comparison expression (different address spaces):
   kernel/sched/sched.h:2032:25: sparse:    struct task_struct [noderef] __rcu *
   kernel/sched/sched.h:2032:25: sparse:    struct task_struct *

vim +1560 kernel/sched/rt.c

  1557	
  1558	static void yield_task_rt(struct rq *rq)
  1559	{
> 1560		struct task_struct *p = rq->curr;
  1561	
  1562		if (p->policy == SCHED_RR)
  1563			p->rt.time_slice = sched_rr_timeslice;
  1564	
  1565		requeue_task_rt(rq, p, 0);
  1566	}
  1567	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

      parent reply	other threads:[~2021-12-22 18:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-22  9:15 zhaoxiu.zeng
2021-12-22 10:40 ` Peter Zijlstra
2021-12-24  1:58   ` Zhaoxiu Zeng
2021-12-22 18:41 ` kernel test robot [this message]

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=202112230234.B6uAyy2x-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=bristot@redhat.com \
    --cc=bsegall@google.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=juri.lelli@redhat.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgorman@suse.de \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=vincent.guittot@linaro.org \
    --cc=zhaoxiu.zeng@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®