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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 18 Sep 2017 07:44:14 -0500 From: Rob Herring <robh@...nel.org> To: Abdul Haleem <abdhalee@...ux.vnet.ibm.com> Cc: linuxppc-dev <linuxppc-dev@...ts.ozlabs.org>, linux-kernel <linux-kernel@...r.kernel.org>, linux-next <linux-next@...r.kernel.org>, Stephen Rothwell <sfr@...b.auug.org.au>, mpe <mpe@...erman.id.au>, Paul Mackerras <paulus@...ba.org> Subject: Re: [linux-next][DLPAR CPU][Oops] Bad kernel stack pointer On Mon, Sep 18, 2017 at 5:08 AM, Abdul Haleem <abdhalee@...ux.vnet.ibm.com> wrote: > 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 I assume this is not something new to 9/15 -next nor only in -next because you also reported that 4.13.0 broke. Can you provide some details on what version worked? 4.12? Rob
Powered by blists - more mailing lists