Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S941637AbcLVRYP (ORCPT ); Thu, 22 Dec 2016 12:24:15 -0500 Received: from mail-it0-f68.google.com ([209.85.214.68]:33526 "EHLO mail-it0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755300AbcLVRYO (ORCPT ); Thu, 22 Dec 2016 12:24:14 -0500 MIME-Version: 1.0 In-Reply-To: <20161222062858.GG4758@dastard> References: <20161214222411.GH4326@dastard> <20161214222953.GI4326@dastard> <20161216185906.t2wmrr6wqjdsrduw@straylight.hirudinean.org> <20161221221638.GD4758@dastard> <20161222001303.nvrtm22szn3hgxar@straylight.hirudinean.org> <20161222051322.GF4758@dastard> <20161222062858.GG4758@dastard> From: Linus Torvalds Date: Thu, 22 Dec 2016 09:24:12 -0800 X-Google-Sender-Auth: _XYgwJtZPZD0yDs9EAAv1Epgdpc Message-ID: Subject: Re: [4.10, panic, regression] iscsi: null pointer deref at iscsi_tcp_segment_done+0x20d/0x2e0 To: Dave Chinner , Thomas Gleixner , Ingo Molnar , Peter Anvin Cc: Linux Kernel Mailing List , "the arch/x86 maintainers" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1926 Lines: 42 On Wed, Dec 21, 2016 at 10:28 PM, Dave Chinner wrote: > > This sort of thing is normally indicative of a memory reclaim or > lock contention problem. Profile showed unusual spinlock contention, > but then I realised there was only one kswapd thread running. > Yup, sure enough, it's caused by a major change in memory reclaim > behaviour: > > [ 0.000000] Zone ranges: > [ 0.000000] DMA [mem 0x0000000000001000-0x0000000000ffffff] > [ 0.000000] DMA32 [mem 0x0000000001000000-0x00000000ffffffff] > [ 0.000000] Normal [mem 0x0000000100000000-0x000000083fffffff] > [ 0.000000] Movable zone start for each node > [ 0.000000] Early memory node ranges > [ 0.000000] node 0: [mem 0x0000000000001000-0x000000000009efff] > [ 0.000000] node 0: [mem 0x0000000000100000-0x00000000bffdefff] > [ 0.000000] node 0: [mem 0x0000000100000000-0x00000003bfffffff] > [ 0.000000] node 0: [mem 0x00000005c0000000-0x00000005ffffffff] > [ 0.000000] node 0: [mem 0x0000000800000000-0x000000083fffffff] > [ 0.000000] Initmem setup node 0 [mem 0x0000000000001000-0x000000083fffffff] > > the numa=fake=4 CLI option is broken. Ok, I think that is independent of anything else. Removing block people and adding the x86 people. I'm not seeing anything at all that would change the fake numa stuff, but maybe the cpu hotplug changes? Thomas/Ingo/Peter - Dave is going away for several months, so you won't get feedback from him, but can you look at this? Or maybe point me towards the right people - I'm seeing no possible relevant changes at all fir x85 numa since 4.9, so it must be some indirect breakage. Dave is using fake-numa to do performance testing in a VM, and it's a big deal for the node optimizations for writeback etc. Do you have any ideas? Dave, if you're still around, can you send out the kernel config file you used... Linus