On Tue, Jun 13, 2017 at 6:34 AM, Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx> wrote: > 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 :) I started to take a stab at it at one point and incorporated some feedback from Torvalds etc, it's here: https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git/commit/?h=chrdev-warn&id=65e5b1e9eb3f777ab7535b74b490e882eeec79d7 It tries to use all "holes" in the chardev major map to shun in a bit more devices when we run out of the high dynamic major range. Making them all dynamic seemed dangerous because I was afraid of userspace ABI breakage because of old userlands with static mknod:s. I lost interest when it turned out that the zeroday QEMU stuff was generating random machines that have no counterpart in the real world, and then the exercise seemed a bit academic. The last failures were due to (AFAICT) some relationship between major and minor numbers that I didn't untangle. If there is interest I could try to revive it. Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
