[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <88CBCB04-43F6-4353-82F7-20A67AD49B65@amacapital.net>
Date: Fri, 20 Jul 2018 11:35:34 -1000
From: Andy Lutomirski <luto@...capital.net>
To: "H.J. Lu" <hjl.tools@...il.com>
Cc: Dave Hansen <dave.hansen@...el.com>,
Dave Jones <davej@...emonkey.org.uk>,
"H. Peter Anvin" <hpa@...or.com>,
LKML <linux-kernel@...r.kernel.org>,
Andy Lutomirski <luto@...nel.org>,
Mel Gorman <mgorman@...e.de>,
Andrew Morton <akpm@...ux-foundation.org>,
Rik van Riel <riel@...riel.com>,
Minchan Kim <minchan@...nel.org>
Subject: Re: Kernel 4.17.4 lockup
> On Jul 16, 2018, at 6:05 AM, H.J. Lu <hjl.tools@...il.com> wrote:
>
>> On Fri, Jul 13, 2018 at 7:08 PM, Andy Lutomirski <luto@...capital.net> wrote:
>> I'm not at all convinced that this is the problem, but the series here
>> will give a better diagnostic if the issue really is an IRQ stack
>> overflow:
>>
>> https://git.kernel.org/pub/scm/linux/kernel/git/luto/linux.git/log/?h=x86/guard_pages
>>
>
> This kernel won't boot with this configure file.
Bah humbug. You’ll need to turn KASAN off (and maybe even compile it out entirely) if you want to test this. I need to bug the KASAN folks to unbreak their interaction with stacks in vmap space. It’s been broken literally forever, but I keep incorrectly imagining that it’s been fixed already.
>
> --
> H.J.
> <config.debug.xz>
Powered by blists - more mailing lists