linux-kernel - Re: [ardb:arm-vmap-stacks 5/20] arch/arm/mm/context.c:112:28: error: no member named 'task' in 'struct thread

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAK8P3a1yRTcRgVD_o7YCwKckePPPcy9Btneh6TC1b_ThUzkmtg@mail.gmail.com>
Date:   Thu, 21 Oct 2021 09:19:49 +0200
From:   Arnd Bergmann <arnd@...nel.org>
To:     Ard Biesheuvel <ardb@...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, Oct 21, 2021 at 9:02 AM Ard Biesheuvel <ardb@...nel.org> wrote:
>
> 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.

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