[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170613041842.GA13308@kroah.com>
Date: Tue, 13 Jun 2017 06:18:42 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Logan Gunthorpe <logang@...tatee.com>
Cc: Bjorn Helgaas <helgaas@...nel.org>,
kernel test robot <fengguang.wu@...el.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
LKP <lkp@...org>, linux-arm-kernel@...ts.infradead.org,
devicetree@...r.kernel.org, linux-doc@...r.kernel.org,
linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org,
Bjorn Helgaas <bhelgaas@...gle.com>, wfg@...ux.intel.com,
Alan Cox <alan@...ux.intel.com>, Arnd Bergmann <arnd@...db.de>,
Linus Walleij <linus.walleij@...aro.org>,
David Airlie <airlied@...ux.ie>,
David Herrmann <dh.herrmann@...il.com>,
Daniel Vetter <daniel.vetter@...ll.ch>
Subject: Re: [Merge tag 'pci-v4.12-changes' of git] 857f864014: BUG: unable
to handle kernel NULL pointer dereference at 00000000000000a8
On Mon, Jun 12, 2017 at 05:34:59PM -0600, Logan Gunthorpe wrote:
> 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.)
What test causes so many major numbers to be allocated? Is this
in-kernel test code? Do you really have a system that requires so many
different drivers that all want a dynamic char major?
thanks,
gre gk-h
Powered by blists - more mailing lists