On Tue, Jan 30, 2018 at 04:33:19PM -0500, Laurence Oberman wrote: > > > 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 > > Hi Bart, > > Can I take your tree and see if this fails for me too, > Your last tree was fine, so did not have this latest stuff. > Can I just pull to what I have Try what we are about to send as a PR: git://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma.git branch wip/for-linus-merged https://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma.git/log/?h=wip/for-linus-merged No guess why a kzalloc will fail. How much is it asking for anyhow? Did the size get out of control for some reason? Jason -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
