linux-kernel - Re: [next] arm64: mte.c:176:17: error: 'struct thread_struct' has no member named 'sctlr

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20201130160052.GF3902@gaia>
Date:   Mon, 30 Nov 2020 16:00:52 +0000
From:   Catalin Marinas <catalin.marinas@....com>
To:     Naresh Kamboju <naresh.kamboju@...aro.org>
Cc:     Linux-Next Mailing List <linux-next@...r.kernel.org>,
        open list <linux-kernel@...r.kernel.org>,
        Linux ARM <linux-arm-kernel@...ts.infradead.org>,
        lkft-triage@...ts.linaro.org, Arnd Bergmann <arnd@...db.de>,
        Vincenzo Frascino <vincenzo.frascino@....com>,
        Stephen Rothwell <sfr@...b.auug.org.au>,
        Will Deacon <will@...nel.org>, andreyknvl@...gle.com,
        Andrew Morton <akpm@...ux-foundation.org>,
        Peter Collingbourne <pcc@...gle.com>, steven.price@....com
Subject: Re: [next] arm64: mte.c:176:17: error: 'struct thread_struct' has no
 member named 'sctlr_tcf0'

On Mon, Nov 30, 2020 at 09:12:58PM +0530, Naresh Kamboju wrote:
> Linux next tag 20201130 arm64 build failed due to below error,
>   - gcc-9, gcc-10 and clang-10 build FAIL
>   - gcc-8 build PASS.
> 
> make --silent --keep-going --jobs=8
> O=/home/tuxbuild/.cache/tuxmake/builds/2/tmp ARCH=arm64
> CROSS_COMPILE=aarch64-linux-gnu- 'CC=sccache aarch64-linux-gnu-gcc'
> 'HOSTCC=sccache gcc'
> arch/arm64/kernel/mte.c: In function 'set_sctlr_el1_tcf0':
> arch/arm64/kernel/mte.c:176:17: error: 'struct thread_struct' has no
> member named 'sctlr_tcf0'
>   176 |  current->thread.sctlr_tcf0 = tcf0;

Thanks for the report. There is a bodged conflict resolution, it should
disappear when Stephen updates the -next tree.

-- 
Catalin