[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8462abee-0a7f-00fb-6111-1f78362ea3f7@deltatee.com>
Date: Tue, 13 Jun 2017 10:25:40 -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:35 PM, Greg Kroah-Hartman wrote:
> Or better yet, just turn all char major allocations into dynamic, which
> would be really good for test systems. I thought someone proposed
> patches for that a long time ago, but I can't find them anymore. That
> would be the simplest solution here.
Would people not complain about that? I would not be surprised if some
crazy application is using hard coded major numbers in userspace. So
such a change could potentially break userspace...
Logan
Powered by blists - more mailing lists