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
| ||
|
Date: Tue, 19 Sep 2017 19:04:09 +0530 From: Abdul Haleem <abdhalee@...ux.vnet.ibm.com> To: Rob Herring <robh@...nel.org> Cc: Stephen Rothwell <sfr@...b.auug.org.au>, linux-kernel <linux-kernel@...r.kernel.org>, linux-next <linux-next@...r.kernel.org>, Paul Mackerras <paulus@...ba.org>, linuxppc-dev <linuxppc-dev@...ts.ozlabs.org> Subject: Re: [linux-next][DLPAR CPU][Oops] Bad kernel stack pointer On Mon, 2017-09-18 at 07:44 -0500, Rob Herring wrote: > 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? [linux-next][DLPAR CPU][Oops] Bad kernel stack pointer [mainline][DLPAR][Oops] OF: ERROR: Bad of_node_put() on /cpus The above issues are not reproducible with 4.12.0 (mainline), it is broken with 4.13.0 and next. -- Regard's Abdul Haleem IBM Linux Technology Centre
Powered by blists - more mailing lists