From: kernel test robot <lkp@intel.com>
To: Xiaolei Wang <xiaolei.wang@windriver.com>,
rafael@kernel.org, pavel@ucw.cz, len.brown@intel.com,
peterz@infradead.org, mingo@kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] freezer,sched: Move state information judgment outside task_call_func
Date: Fri, 8 Dec 2023 03:30:04 +0800 [thread overview]
Message-ID: <202312080347.yJvIjGb3-lkp@intel.com> (raw)
In-Reply-To: <20231207111634.667057-1-xiaolei.wang@windriver.com>
Hi Xiaolei,
kernel test robot noticed the following build errors:
[auto build test ERROR on linus/master]
[also build test ERROR on v6.7-rc4 next-20231207]
[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/Xiaolei-Wang/freezer-sched-Move-state-information-judgment-outside-task_call_func/20231207-191924
base: linus/master
patch link: https://lore.kernel.org/r/20231207111634.667057-1-xiaolei.wang%40windriver.com
patch subject: [PATCH] freezer,sched: Move state information judgment outside task_call_func
config: arm-defconfig (https://download.01.org/0day-ci/archive/20231208/202312080347.yJvIjGb3-lkp@intel.com/config)
compiler: clang version 14.0.6 (https://github.com/llvm/llvm-project.git f28c006a5895fc0e329fe15fead81e37457cb1d1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231208/202312080347.yJvIjGb3-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/202312080347.yJvIjGb3-lkp@intel.com/
All errors (new ones prefixed by >>):
>> kernel/freezer.c:125:30: error: no member named 'lockdep_depth' in 'struct task_struct'
p_check->lockdep_depth = p->lockdep_depth;
~ ^
1 error generated.
vim +125 kernel/freezer.c
107
108 static int __set_task_frozen(struct task_struct *p, void *arg)
109 {
110 unsigned int state = READ_ONCE(p->__state);
111 struct task_freeze_check *p_check = arg;
112
113 if (p->on_rq)
114 return 0;
115
116 if (p != current && task_curr(p))
117 return 0;
118
119 if (!(state & (TASK_FREEZABLE | __TASK_STOPPED | __TASK_TRACED)))
120 return 0;
121
122 p->saved_state = p->__state;
123 WRITE_ONCE(p->__state, TASK_FROZEN);
124 p_check->state = p->__state;
> 125 p_check->lockdep_depth = p->lockdep_depth;
126 return TASK_FROZEN;
127 }
128
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-12-07 19:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-07 11:16 [PATCH] freezer,sched: Move state information judgment outside task_call_func Xiaolei Wang
2023-12-07 12:35 ` Peter Zijlstra
2023-12-07 19:30 ` kernel test robot [this message]
2023-12-07 21:06 ` kernel test robot
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=202312080347.yJvIjGb3-lkp@intel.com \
--to=lkp@intel.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mingo@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pavel@ucw.cz \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=xiaolei.wang@windriver.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