From: Sachin Sant <sachinp@linux.ibm.com>
To: Randy Dunlap <rdunlap@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>
Cc: broonie@kernel.org, mhocko@suse.cz,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-mm@kvack.org, open list <linux-kernel@vger.kernel.org>,
mm-commits@vger.kernel.org,
linux-um <linux-um@lists.infradead.org>,
"Paul E. McKenney" <paulmck@kernel.org>,
Richard Weinberger <richard@nod.at>,
Johannes Berg <johannes@sipsolutions.net>
Subject: Re: mmotm 2022-03-16-17-42 uploaded (uml sub-x86_64, sched/fair, RCU)
Date: Fri, 18 Mar 2022 10:02:40 +0530 [thread overview]
Message-ID: <4E00E70C-9605-4BE7-AB15-9ABE05CBAE4B@linux.ibm.com> (raw)
In-Reply-To: <99d45fe4-53ca-b966-e140-cd68b731292a@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 2597 bytes --]
>> I still can't reproduce this :(
>>
>>> This fixes the build error for me when CONFIG_PSI=n.
>>
>> I have CONFIG_PSI=n
>
> There was also this report about linux-next, also with CONFIG_PSI=n:
>
> https://lore.kernel.org/all/EF33D230-9A8F-41C5-A38D-95128603224F@linux.ibm.com/
Yes, I can still recreate this build error (against 5.17.0-rc8-next-20220317)
CC kernel/sched/fair.o
In file included from ./arch/powerpc/include/generated/asm/rwonce.h:1,
from ./include/linux/compiler.h:248,
from ./include/linux/kernel.h:20,
from ./include/linux/cpumask.h:10,
from ./include/linux/energy_model.h:4,
from kernel/sched/fair.c:23:
./include/linux/psi.h: In function 'cgroup_move_task':
./include/linux/rcupdate.h:414:36: error: dereferencing pointer to incomplete type 'struct css_set'
#define RCU_INITIALIZER(v) (typeof(*(v)) __force __rcu *)(v)
^~~~
./include/asm-generic/rwonce.h:55:33: note: in definition of macro '__WRITE_ONC'
*(volatile typeof(x) *)&(x) = (val); \
^~~
./arch/powerpc/include/asm/barrier.h:74:2: note: in expansion of macro 'WRITE_ONCE'
WRITE_ONCE(*p, v); \
^~~~~~~~~~
./include/asm-generic/barrier.h:164:55: note: in expansion of macro '__smp_store_release'
#define smp_store_release(p, v) do { kcsan_release(); __smp_store_release(p, v); } while (0)
^~~~~~~~~~~~~~~~~~~
./include/linux/rcupdate.h:455:3: note: in expansion of macro 'smp_store_releas'
smp_store_release(&p, RCU_INITIALIZER((typeof(p))_r_a_p__v)); \
^~~~~~~~~~~~~~~~~
./include/linux/rcupdate.h:455:25: note: in expansion of macro 'RCU_INITIALIZER'
smp_store_release(&p, RCU_INITIALIZER((typeof(p))_r_a_p__v)); \
^~~~~~~~~~~~~~~
./include/linux/psi.h:58:2: note: in expansion of macro 'rcu_assign_pointer'
rcu_assign_pointer(p->cgroups, to);
^~~~~~~~~~~~~~~~~~
make[2]: *** [scripts/Makefile.build:310: kernel/sched/fair.o] Error 1
make[1]: *** [scripts/Makefile.build:638: kernel/sched] Error 2
make: *** [Makefile:1991: kernel] Error 2
As mentioned by Randy, this build break was introduced in next-20220316.
Git bisect points to:
commit c4ad6fcb67c42d65481c85733c8009c8afdfdf4e (refs/bisect/bad)
sched/headers: Reorganize, clean up and optimize kernel/sched/fair.c dependencies
The change suggested by Randy works for me.
I have attached .config for reference.
-Sachin
[-- Attachment #2: config_next.gz --]
[-- Type: application/x-gzip, Size: 41403 bytes --]
next prev parent reply other threads:[~2022-03-18 4:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-17 0:43 mmotm 2022-03-16-17-42 uploaded Andrew Morton
2022-03-17 4:21 ` mmotm 2022-03-16-17-42 uploaded (uml sub-x86_64, sched/fair, RCU) Randy Dunlap
2022-03-17 4:27 ` Randy Dunlap
2022-03-17 4:30 ` Andrew Morton
2022-03-17 4:52 ` Randy Dunlap
2022-03-17 13:43 ` Paul E. McKenney
2022-03-17 23:51 ` Andrew Morton
2022-03-18 0:10 ` Randy Dunlap
2022-03-18 3:56 ` Randy Dunlap
2022-03-18 4:32 ` Sachin Sant [this message]
2022-03-17 4:24 ` mmotm 2022-03-16-17-42 uploaded (drivers/iio/afe/iio-rescale.o) Randy Dunlap
2022-03-17 4:37 ` mmotm 2022-03-16-17-42 uploaded (drivers/pinctrl/nuvoton/pinctrl-wpcm450.c) Randy Dunlap
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=4E00E70C-9605-4BE7-AB15-9ABE05CBAE4B@linux.ibm.com \
--to=sachinp@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=johannes@sipsolutions.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=mhocko@suse.cz \
--cc=mm-commits@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=rdunlap@infradead.org \
--cc=richard@nod.at \
--cc=sfr@canb.auug.org.au \
/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