From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [android-common:android12-5.10 1/1] kernel/sched/rt.c:1385:33: error: 'struct <anonymous>' has no member named 'next'
Date: Fri, 26 Feb 2021 04:34:01 +0800 [thread overview]
Message-ID: <202102260459.kodPy6re-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2509 bytes --]
tree: https://android.googlesource.com/kernel/common android12-5.10
head: da5f3cd37802e4d68861422ba4503a4e2d58aa23
commit: da5f3cd37802e4d68861422ba4503a4e2d58aa23 [1/1] ANDROID: sched/rt: Add support for rt sync wakeups
config: x86_64-randconfig-s021-20210225 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.3-229-g60c1f270-dirty
git remote add android-common https://android.googlesource.com/kernel/common
git fetch --no-tags android-common android12-5.10
git checkout da5f3cd37802e4d68861422ba4503a4e2d58aa23
# save the attached .config to linux build tree
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
kernel/sched/rt.c:670:6: warning: no previous prototype for 'sched_rt_bandwidth_account' [-Wmissing-prototypes]
670 | bool sched_rt_bandwidth_account(struct rt_rq *rt_rq)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
kernel/sched/rt.c: In function 'should_honor_rt_sync':
>> kernel/sched/rt.c:1385:33: error: 'struct <anonymous>' has no member named 'next'
1385 | p->prio <= rq->rt.highest_prio.next &&
| ^
kernel/sched/rt.c:1387:1: error: control reaches end of non-void function [-Werror=return-type]
1387 | }
| ^
cc1: some warnings being treated as errors
vim +1385 kernel/sched/rt.c
1374
1375 #if defined CONFIG_SMP || defined CONFIG_RT_GROUP_SCHED
1376 static inline bool should_honor_rt_sync(struct rq *rq, struct task_struct *p,
1377 bool sync)
1378 {
1379 /*
1380 * If the waker is CFS, then an RT sync wakeup would preempt the waker
1381 * and force it to run for a likely small time after the RT wakee is
1382 * done. So, only honor RT sync wakeups from RT wakers.
1383 */
1384 return sync && task_has_rt_policy(rq->curr) &&
> 1385 p->prio <= rq->rt.highest_prio.next &&
1386 rq->rt.rt_nr_running <= 2;
1387 }
1388 #else
1389 static inline bool should_honor_rt_sync(struct rq *rq, struct task_struct *p,
1390 bool sync)
1391 {
1392 return 0;
1393 }
1394 #endif
1395
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 31653 bytes --]
reply other threads:[~2021-02-25 20:34 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=202102260459.kodPy6re-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
/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.