On Mon, Jun 12, 2017 at 10:29:20PM -0600, Logan Gunthorpe wrote:
On 12/06/17 10:18 PM, Greg Kroah-Hartman wrote:
quoted
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.
Ah, that makes sense. Well, someone can always work on expanding the
range of dynamic char major numbers if they are running out of them on a
real system, I'll gladly take patches for that :)
thanks,
greg k-h