linux-kernel - RE: kernel panics with 4.14.X versions

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: <KL1P15301MB000619E372AA3A2FD505ADA5BFB50@KL1P15301MB0006.APCP153.PROD.OUTLOOK.COM>
Date:   Thu, 19 Apr 2018 21:37:25 +0000
From:   Dexuan Cui <decui@...rosoft.com>
To:     Jan Kara <jack@...e.cz>,
        Pavlos Parissis <pavlos.parissis@...il.com>,
        Haiyang Zhang <haiyangz@...rosoft.com>,
        Robert Kolchmeyer <rkolchmeyer@...gle.com>
CC:     Guillaume Morin <guillaume@...infr.org>,
        "stable@...r.kernel.org" <stable@...r.kernel.org>,
        "jack@...e.com" <jack@...e.com>,
        "linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "mszeredi@...hat.com" <mszeredi@...hat.com>,
        Robert Kolchmeyer <rkolchmeyer@...gle.com>
Subject: RE: kernel panics with 4.14.X versions

> From: Jan Kara
> Sent: Thursday, April 19, 2018 13:23
> Good news guys, Robert has just spotted a bug which looks like what I'd
> expect can cause your lockups / crashes. I've merged his patch to my tree
> and will push it to Linus for -rc3 so eventually it should land in
> appropriate stable trees as well. If you are too eager to test it out, it
> is attached for you to try.
> 
> Jan Kara

The patch's changelog says "... this behavior results in a kernel panic." 
This sounds like a reference to corrupt memory causes a page fault or
general protection fault.

But what I saw is only a lockup rather than a kernel panic:
watchdog: BUG: soft lockup - CPU#10 stuck for 22s! [java:87260]"

So I guess what I saw can be a different unresolved issue?

-- Dexuan