From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android16-6.12 0/9] kernel/sched/deadline.c:2689:25: error: no member named 'pushable_dl_tasks' in 'struct task_struct'
Date: Fri, 10 Apr 2026 19:24:54 +0800 [thread overview]
Message-ID: <202604101944.7DfbTtk4-lkp@intel.com> (raw)
tree: https://android.googlesource.com/kernel/common android16-6.12
head: 91e49117396d06326d151f97f382c6d93a267bea
commit: 02153dcaf1c62548c34d347291c37a9070f163aa [0/9] ANDROID: sched/deadline: Avoid double enqueue_pushable_dl_task() warning
config: x86_64-buildonly-randconfig-002-20260410 (https://download.01.org/0day-ci/archive/20260410/202604101944.7DfbTtk4-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260410/202604101944.7DfbTtk4-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/202604101944.7DfbTtk4-lkp@intel.com/
Note: the android-common/android16-6.12 HEAD 91e49117396d06326d151f97f382c6d93a267bea builds fine.
It only hurts bisectability.
All errors (new ones prefixed by >>):
In file included from kernel/sched/build_policy.c:60:
>> kernel/sched/deadline.c:2689:25: error: no member named 'pushable_dl_tasks' in 'struct task_struct'
2689 | if (!RB_EMPTY_NODE(&p->pushable_dl_tasks))
| ~ ^
include/linux/rbtree.h:34:4: note: expanded from macro 'RB_EMPTY_NODE'
34 | ((node)->__rb_parent_color == (unsigned long)(node))
| ^~~~
In file included from kernel/sched/build_policy.c:60:
>> kernel/sched/deadline.c:2689:25: error: no member named 'pushable_dl_tasks' in 'struct task_struct'
2689 | if (!RB_EMPTY_NODE(&p->pushable_dl_tasks))
| ~ ^
include/linux/rbtree.h:34:48: note: expanded from macro 'RB_EMPTY_NODE'
34 | ((node)->__rb_parent_color == (unsigned long)(node))
| ^~~~
2 errors generated.
vim +2689 kernel/sched/deadline.c
2661
2662 static void put_prev_task_dl(struct rq *rq, struct task_struct *p, struct task_struct *next)
2663 {
2664 struct sched_dl_entity *dl_se = &p->dl;
2665 struct dl_rq *dl_rq = &rq->dl;
2666
2667 if (on_dl_rq(&p->dl))
2668 update_stats_wait_start_dl(dl_rq, dl_se);
2669
2670 update_curr_dl(rq);
2671
2672 update_dl_rq_load_avg(rq_clock_pelt(rq), rq, 1);
2673
2674 if (task_is_blocked(p))
2675 return;
2676
2677 /*
2678 * With proxy-exec its possible the following call
2679 * chain from update_curr_dl() called above has already
2680 * added us to the pushable list:
2681 * update_curr_dl()
2682 * -> update_curr_dl_se()
2683 * -> enqueue_task_dl()
2684 * -> enqueue_pushable_dl_task()
2685 *
2686 * So check if we're already added to make sure we don't
2687 * get added twice
2688 */
> 2689 if (!RB_EMPTY_NODE(&p->pushable_dl_tasks))
2690 return;
2691
2692 if (on_dl_rq(&p->dl) && p->nr_cpus_allowed > 1)
2693 enqueue_pushable_dl_task(rq, p);
2694 }
2695
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-04-10 11:25 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=202604101944.7DfbTtk4-lkp@intel.com \
--to=lkp@intel.com \
--cc=cros-kernel-buildreports@googlegroups.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.