Re: [PATCH rdma-next v7 0/8] RDMA resource tracking

[Bart Van Assche <Bart.VanAssche-Sjgp3cTcYWE@public.gmane.org>]

On Tue, 2018-01-30 at 13:48 -0700, Jason Gunthorpe wrote:
> Ok, I think that is the only likely thing recently..
> 
> But your print above must be caused by this line, right:
> 
> static struct srp_fr_pool *srp_create_fr_pool(struct ib_device *device,
>                                               struct ib_pd *pd, int pool_size,
>                                               int max_page_list_len)
> {
>         ret = -ENOMEM;
>         pool = kzalloc(sizeof(struct srp_fr_pool) +
>                        pool_size * sizeof(struct srp_fr_desc), GFP_KERNEL);
>         if (!pool)
>                 goto err;
> 
> Since you didn't report the ib_alloc_mr() print it can't be the other
> ENOMEM case?
> 
> Hard to see how that interesects with resource tracking.. Are you
> thinking memory corruption?

Hello Jason,

I don't see any reason to suspect memory corruption. kmemleak isn't reporting
any memory leaks. Maybe memory fragmentation has increased?

Thanks,

Bart.