[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK8P3a3uOV=AMmOTP09rBhyq2zJutDJiof-4uQ-7MbX9xyVivg@mail.gmail.com>
Date: Thu, 21 Oct 2021 08:55:09 +0200
From: Arnd Bergmann <arnd@...nel.org>
To: kernel test robot <lkp@...el.com>
Cc: Ard Biesheuvel <ardb@...nel.org>, 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 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.
Arnd
Powered by blists - more mailing lists