linux-kernel - Re: [linux-next][DLPAR CPU][Oops] Bad kernel stack pointer

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <878th9lhpe.fsf@concordia.ellerman.id.au>
Date:   Wed, 20 Sep 2017 21:42:21 +1000
From:   Michael Ellerman <mpe@...erman.id.au>
To:     Abdul Haleem <abdhalee@...ux.vnet.ibm.com>,
        linuxppc-dev <linuxppc-dev@...ts.ozlabs.org>
Cc:     linux-kernel <linux-kernel@...r.kernel.org>,
        linux-next <linux-next@...r.kernel.org>,
        Stephen Rothwell <sfr@...b.auug.org.au>,
        Rob Herring <robh@...nel.org>,
        Paul Mackerras <paulus@...ba.org>
Subject: Re: [linux-next][DLPAR CPU][Oops] Bad kernel stack pointer

Abdul Haleem <abdhalee@...ux.vnet.ibm.com> writes:

> Hi,
>
> Dynamic CPU remove operation resulted in Kernel Panic on today's
> next-20170915 kernel.
>
> Machine Type: Power 7 PowerVM LPAR
> Kernel : 4.13.0-next-20170915
> config : attached
> test: DLPAR CPU remove
>
>
> dmesg logs:
> ----------
> cpu 37 (hwid 37) Ready to die...
> cpu 38 (hwid 38) Ready to die...
> cpu 39 (hwid 39)
> ******* RTAS CReady to die...
> ALL BUFFER CORRUPTION *******

Cool. Does that come from RTAS itself? I have never seen that happen
before.

Is this easily reproducible?

cheers