On Mon, 2017-06-12 at 17:34 -0600, Logan Gunthorpe wrote: > Hey, > > Ok, I dug into this bug and I know what's going on. Unfortunately, > it's > a mess of a couple issues and I don't know what correct the > solution(s) > is(are). > > 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.) > If you dump the list of majors and drivers do they all look valid or is there any corruption or repetition that looks odd (wondering if we've got too many devices or a leak) ? Alan