Messages in this thread | | | From | Arnd Bergmann <> | Date | Thu, 21 Oct 2021 09:19:49 +0200 | Subject | Re: [ardb:arm-vmap-stacks 5/20] arch/arm/mm/context.c:112:28: error: no member named 'task' in 'struct thread_info' |
| |
On Thu, Oct 21, 2021 at 9:02 AM Ard Biesheuvel <ardb@kernel.org> wrote: > > On Thu, 21 Oct 2021 at 08:55, Arnd Bergmann <arnd@kernel.org> wrote: > > > > On Tue, Oct 5, 2021 at 4:03 AM kernel test robot <lkp@intel.com> wrote: > > > > > > > > All errors (new ones prefixed by >>): > > > > > > >> arch/arm/mm/context.c:112:28: error: no member named 'task' in 'struct thread_info' > > > pid = task_pid_nr(thread->task) << ASID_BITS; > > > ~~~~~~ ^ > > > 1 error generated. > > > > I ran into this as well on my randconfig builds, though it happens very rarely. > > > > Apparently CONFIG_THREAD_INFO_IN_TASK is incompatible with > > CONFIG_PID_IN_CONTEXTIDR, but should be easy to fix by changing that > > one line to do the right thing. > > > > None of the existing configs enable that, so that is why I never saw > this even with all the kernelci coverage.
Right, I have no idea what makes this configuration so rare, it took me hundreds of randconfig builds before I first ran into it.
Arnd
| |