linux-kernel - Re: linux-next: runtime warnings from qemu run

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: <0dc1af93-3b5f-6147-359a-33980591c73f@csgroup.eu>
Date:   Fri, 26 Nov 2021 06:48:36 +0100
From:   Christophe Leroy <christophe.leroy@...roup.eu>
To:     Stephen Rothwell <sfr@...b.auug.org.au>,
        Michael Ellerman <mpe@...erman.id.au>,
        PowerPC <linuxppc-dev@...ts.ozlabs.org>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: runtime warnings from qemu run



Le 26/11/2021 à 06:17, Stephen Rothwell a écrit :
> Hi all,
> 
> My qemu boot test (pseries_le_defconfig) produces these new messages:
> 
> code-patching: test failed at line 444
> code-patching: test failed at line 447
> code-patching: test failed at line 450
> code-patching: test failed at line 453
> code-patching: test failed at line 456
> code-patching: test failed at line 461
> code-patching: test failed at line 466
> code-patching: test failed at line 471
> code-patching: test failed at line 476
> code-patching: test failed at line 493
> code-patching: test failed at line 533
> code-patching: test failed at line 536
> code-patching: test failed at line 539
> code-patching: test failed at line 542
> code-patching: test failed at line 545
> code-patching: test failed at line 553
> code-patching: test failed at line 558
> code-patching: test failed at line 563
> code-patching: test failed at line 568
> code-patching: test failed at line 585
> code-patching: test failed at line 605
> code-patching: test failed at line 609
> code-patching: test failed at line 618
> code-patching: test failed at line 619
> code-patching: test failed at line 620
> code-patching: test failed at line 629
> code-patching: test failed at line 630
> code-patching: test failed at line 631
> code-patching: test failed at line 640
> code-patching: test failed at line 641
> code-patching: test failed at line 650
> code-patching: test failed at line 651
> code-patching: test failed at line 661
> code-patching: test failed at line 665
> code-patching: test failed at line 675
> code-patching: test failed at line 676
> code-patching: test failed at line 677
> code-patching: test failed at line 687
> code-patching: test failed at line 688
> code-patching: test failed at line 689
> code-patching: test failed at line 699
> code-patching: test failed at line 700
> code-patching: test failed at line 710
> code-patching: test failed at line 711
> 
> Maybe caused by commit
> 
>    8b8a8f0ab3f5 ("powerpc/code-patching: Improve verification of patchability")

Yes, Nic proposed a series to fix that: 
https://patchwork.ozlabs.org/project/linuxppc-dev/patch/20211126032249.1652080-1-npiggin@gmail.com/


> 
> As an presumably unrelated aside, we seem to be using a bit more stack
> space as well
> 
> - mount (54) used greatest stack depth: 12512 bytes left
> - mount (55) used greatest stack depth: 12032 bytes left
> + mount (54) used greatest stack depth: 10608 bytes left
>