On Tue, Oct 19, 2021 at 08:26:56AM +0800, wangyugui wrote: > When CONFIG_PROVE_LOCKING=y, one kmalloc of infiniband hit the max alloc size limitation. > > WARNING: CPU: 36 PID: 8 at mm/page_alloc.c:5350 __alloc_pages+0x27e/0x3e0 > Call Trace: > kmalloc_order+0x2a/0xb0 > kmalloc_order_trace+0x19/0xf0 > __kmalloc+0x231/0x270 > ib_setup_port_attrs+0xd8/0x870 [ib_core] > ib_register_device+0x419/0x4e0 [ib_core] > bnxt_re_task+0x208/0x2d0 [bnxt_re] > > change this kmalloc to kvmalloc to support CONFIG_PROVE_LOCKING=y > > Signed-off-by: wangyugui <wangyugui@xxxxxxxxxxxx> > --- > drivers/infiniband/core/sysfs.c | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) Huh? what causes ib_port to get larger than MAX_ORDER? The only array is attrs_list and I don't see something that scales with Jason
