Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752441AbdFMLsb (ORCPT ); Tue, 13 Jun 2017 07:48:31 -0400 Received: from mga05.intel.com ([192.55.52.43]:49201 "EHLO mga05.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752033AbdFMLs3 (ORCPT ); Tue, 13 Jun 2017 07:48:29 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.39,338,1493708400"; d="scan'208";a="114280287" Message-ID: <1497354494.5693.1.camel@linux.intel.com> Subject: Re: [Merge tag 'pci-v4.12-changes' of git] 857f864014: BUG: unable to handle kernel NULL pointer dereference at 00000000000000a8 From: Alan Cox To: Logan Gunthorpe , Bjorn Helgaas Cc: kernel test robot , Linus Torvalds , LKP , linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, linux-doc@vger.kernel.org, linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org, Bjorn Helgaas , wfg@linux.intel.com, Greg Kroah-Hartman , Arnd Bergmann , Linus Walleij , David Airlie , David Herrmann , Daniel Vetter Date: Tue, 13 Jun 2017 12:48:14 +0100 In-Reply-To: <61e11e67-6c1b-ef1e-5fb8-a7c9efb17666@deltatee.com> References: <5933fe2d.V33ODGPU9noDVuyF%fengguang.wu@intel.com> <20170606175552.GA12672@bhelgaas-glaptop.roam.corp.google.com> <20170612200852.GA28578@bhelgaas-glaptop.roam.corp.google.com> <61e11e67-6c1b-ef1e-5fb8-a7c9efb17666@deltatee.com> Organization: Intel Corporation Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.20.5 (3.20.5-1.fc24) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 755 Lines: 23 On Mon, 2017-06-12 at 17:34 -0600, Logan Gunthorpe wrote: > Hey, > > Ok, I dug into this bug and I know what's going on. Unfortunately, > it's > a mess of a couple issues and I don't know what correct the > solution(s) > is(are). > > 1) The test we are looking at is overrunning the dynamic char dev > major > numbers by a lot. On a successful run, it gets down to 216 where the > limit is 234. Thus, there are 18 too many major numbers assigned and > the > fact that this test used to work is really just luck. (I've cc'd > developers from 49db08c3 for this issue.) > If you dump the list of majors and drivers do they all look valid or is there any corruption or repetition that looks odd (wondering if we've got too many devices or a leak) ? Alan