From: Chen Zhongjin <chenzhongjin@huawei.com>
To: kernel test robot <lkp@intel.com>, <linux-kernel@vger.kernel.org>
Cc: <oe-kbuild-all@lists.linux.dev>, <mingo@redhat.com>,
<peterz@infradead.org>, <juri.lelli@redhat.com>,
<vincent.guittot@linaro.org>, <dietmar.eggemann@arm.com>,
<rostedt@goodmis.org>, <bsegall@google.com>, <mgorman@suse.de>,
<bristot@redhat.com>, <vschneid@redhat.com>,
<rmk+kernel@armlinux.org.uk>, <geert@linux-m68k.org>,
<keescook@chromium.org>
Subject: Re: [PATCH] wchan: Fix get_wchan() when task in schedule
Date: Fri, 31 Mar 2023 09:08:41 +0800 [thread overview]
Message-ID: <c3ad2c5e-4368-aaec-6d69-ed24228f8ad2@huawei.com> (raw)
In-Reply-To: <202303302125.7Ku9P7v5-lkp@intel.com>
It seems because of !CONFIG_SMP. I'll push a new version.
On 2023/3/30 21:53, kernel test robot wrote:
> Hi Chen,
>
> Thank you for the patch! Yet something to improve:
>
> [auto build test ERROR on tip/sched/core]
> [also build test ERROR on linus/master v6.3-rc4 next-20230330]
> [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/Chen-Zhongjin/wchan-Fix-get_wchan-when-task-in-schedule/20230330-201555
> patch link: https://lore.kernel.org/r/20230330121238.176534-1-chenzhongjin%40huawei.com
> patch subject: [PATCH] wchan: Fix get_wchan() when task in schedule
> config: sh-allmodconfig (https://download.01.org/0day-ci/archive/20230330/202303302125.7Ku9P7v5-lkp@intel.com/config)
> compiler: sh4-linux-gcc (GCC) 12.1.0
> reproduce (this is a W=1 build):
> wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> # https://github.com/intel-lab-lkp/linux/commit/d5fd727a071ab3c2241f858e77c2ae5bb3cec6f3
> git remote add linux-review https://github.com/intel-lab-lkp/linux
> git fetch --no-tags linux-review Chen-Zhongjin/wchan-Fix-get_wchan-when-task-in-schedule/20230330-201555
> git checkout d5fd727a071ab3c2241f858e77c2ae5bb3cec6f3
> # save the config file
> mkdir build_dir && cp config build_dir/.config
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=sh olddefconfig
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=sh SHELL=/bin/bash kernel/
>
> If you fix the issue, kindly add following tag where applicable
> | Reported-by: kernel test robot <lkp@intel.com>
> | Link: https://lore.kernel.org/oe-kbuild-all/202303302125.7Ku9P7v5-lkp@intel.com/
>
> All errors (new ones prefixed by >>):
>
> kernel/sched/core.c: In function 'get_wchan':
>>> kernel/sched/core.c:2060:28: error: 'struct task_struct' has no member named 'on_cpu'
> 2060 | !p->on_rq && !p->on_cpu)
> | ^~
>
>
> vim +2060 kernel/sched/core.c
>
> 2046
> 2047 unsigned long get_wchan(struct task_struct *p)
> 2048 {
> 2049 unsigned long ip = 0;
> 2050 unsigned int state;
> 2051
> 2052 if (!p || p == current)
> 2053 return 0;
> 2054
> 2055 /* Only get wchan if task is blocked and we can keep it that way. */
> 2056 raw_spin_lock_irq(&p->pi_lock);
> 2057 state = READ_ONCE(p->__state);
> 2058 smp_rmb(); /* see try_to_wake_up() */
> 2059 if (state != TASK_RUNNING && state != TASK_WAKING &&
>> 2060 !p->on_rq && !p->on_cpu)
> 2061 ip = __get_wchan(p);
> 2062 raw_spin_unlock_irq(&p->pi_lock);
> 2063
> 2064 return ip;
> 2065 }
> 2066
>
next prev parent reply other threads:[~2023-03-31 1:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 12:12 Chen Zhongjin
2023-03-30 13:53 ` kernel test robot
2023-03-31 1:08 ` Chen Zhongjin [this message]
2023-03-30 16:58 ` 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=c3ad2c5e-4368-aaec-6d69-ed24228f8ad2@huawei.com \
--to=chenzhongjin@huawei.com \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=geert@linux-m68k.org \
--cc=juri.lelli@redhat.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=peterz@infradead.org \
--cc=rmk+kernel@armlinux.org.uk \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.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®