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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Jan 30, 2018 at 09:40:14PM +0000, Bart Van Assche wrote:
> On Tue, 2018-01-30 at 16:33 -0500, Laurence Oberman wrote:
> > 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
> 
> Hello Laurence,
> 
> So far I have seen this behavior only inside a VM but not yet on a system
> with more memory than the VM. This issue may be specific to the memory size
> of the VM. I think we should try to isolate furhter what caused this before
> trying to reproduce it on more setups.

Did you get an oops print related a kalloc failure?

Or am I wrong and the ENOMEM is coming from someplace else?

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



[Index of Archives]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Photo]     [Yosemite News]     [Yosemite Photos]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux