[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMj1kXHem8-qpNswtRcEKErncpO65JpQJQL3-8k_-qzUm4S4_Q@mail.gmail.com>
Date: Thu, 21 Oct 2021 09:02:32 +0200
From: Ard Biesheuvel <ardb@...nel.org>
To: Arnd Bergmann <arnd@...nel.org>
Cc: kernel test robot <lkp@...el.com>, llvm@...ts.linux.dev,
kbuild-all@...ts.01.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Keith Packard <keithpac@...zon.com>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>
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, 21 Oct 2021 at 08:55, Arnd Bergmann <arnd@...nel.org> wrote:
>
> On Tue, Oct 5, 2021 at 4:03 AM kernel test robot <lkp@...el.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.
I'll send a patch to fix this.
Powered by blists - more mailing lists