linux-kernel - Re: [kbuild-all] Re: [tip:locking/core 4/5] vmlinux.o: warning: objtool: do_machine_check()+0x419: call to mca_msr

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: <FE9FFA59-C8C3-4F71-9A63-6AD95EA248B4@alien8.de>
Date:   Thu, 17 Mar 2022 12:29:33 +0000
From:   Boris Petkov <bp@...en8.de>
To:     "Chen, Rong A" <rong.a.chen@...el.com>,
        kernel test robot <lkp@...el.com>
CC:     kbuild-all@...ts.01.org, linux-kernel@...r.kernel.org,
        x86@...nel.org, Peter Zijlstra <peterz@...radead.org>
Subject: Re: [kbuild-all] Re: [tip:locking/core 4/5] vmlinux.o: warning: objtool: do_machine_check()+0x419: call to mca_msr_reg() leaves .noinstr.text section

On March 17, 2022 12:32:32 AM UTC, "Chen, Rong A" <rong.a.chen@...el.com> wrote:
>Thanks for the explanation, should we skip testing the locking/core 
>branch next time?

Nah, no need to skip it - this "split fix" will go to Linus next week and you can do your regular testing after that like before. 

Thx.


-- 
Sent from a small device: formatting sux and brevity is inevitable.