From: kernel test robot <lkp@intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
x86@kernel.org, Daniel Bristot de Oliveira <bristot@redhat.com>
Subject: [tip:sched/core 7/10] runqslower.bpf.c:77:12: error: no member named 'state' in 'struct task_struct'
Date: Thu, 24 Jun 2021 04:18:40 +0800 [thread overview]
Message-ID: <202106240431.pQhQXlhJ-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1182 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git sched/core
head: 0213b7083e81f4acd69db32cb72eb4e5f220329a
commit: 2f064a59a11ff9bc22e52e9678bc601404c7cb34 [7/10] sched: Change task_struct::state
config: x86_64-rhel-8.3-kselftests (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?id=2f064a59a11ff9bc22e52e9678bc601404c7cb34
git remote add tip https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
git fetch --no-tags tip sched/core
git checkout 2f064a59a11ff9bc22e52e9678bc601404c7cb34
# save the attached .config to linux build tree
make W=1 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 >>):
>> runqslower.bpf.c:77:12: error: no member named 'state' in 'struct task_struct'
if (prev->state == TASK_RUNNING)
~~~~ ^
1 error generated.
---
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: 41910 bytes --]
reply other threads:[~2021-06-23 20:19 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=202106240431.pQhQXlhJ-lkp@intel.com \
--to=lkp@intel.com \
--cc=bristot@redhat.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=x86@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).