[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f6322f70-7ca7-abf6-b947-4cbbfd598948@deltatee.com>
Date: Mon, 12 Jun 2017 22:29:20 -0600
From: Logan Gunthorpe <logang@...tatee.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
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 12/06/17 10:18 PM, Greg Kroah-Hartman wrote:
> 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?
This is a 0day kernel robot test. I'm not sure the motivations of its
design but it seems to be similar to an allyesconfig. So all/most
modules are compiled in and allocating their char device regions on boot
of a qemu instance.
Logan
Powered by blists - more mailing lists