On Sun, May 20, 2018 at 10:35:29PM +0000, Bart Van Assche wrote: > On Sun, 2018-05-20 at 18:31 -0400, Kent Overstreet wrote: > > On Sun, May 20, 2018 at 10:19:13PM +0000, Bart Van Assche wrote: > > > On Sun, 2018-05-20 at 18:17 -0400, Kent Overstreet wrote: > > > > On Fri, May 18, 2018 at 03:12:27PM +0000, Bart Van Assche wrote: > > > > > On Fri, 2018-05-18 at 05:06 -0400, Kent Overstreet wrote: > > > > > > On Thu, May 17, 2018 at 08:54:57PM +0000, Bart Van Assche wrote: > > > > > > > With Jens' latest for-next branch I hit the kernel warning shown below. Can > > > > > > > you have a look? > > > > > > > > > > > > Any hints on how to reproduce it? > > > > > > > > > > Sure. This is how I triggered it: > > > > > * Clone https://github.com/bvanassche/srp-test. > > > > > * Follow the instructions in README.md. > > > > > * Run srp-test/run_tests -c -r 10 > > > > > > > > Can you bisect it? I don't have infiniband hardware handy... > > > > > > Hello Kent, > > > > > > Have you noticed that the test I described uses the rdma_rxe driver and hence that > > > no InfiniBand hardware is needed to run that test? > > > > No, I'm not terribly familiar with infiniband stuff.... > > > > Do you have some sort of self contained test/qemu recipe? I would really rather > > not have to figure out how to configure multipath, and infiniband, and I'm not > > even sure what else is needed based on that readme... > > Hello Kent, > > Please have another look at the srp-test README. The instructions in that document > are easy to follow. No multipath nor any InfiniBand knowledge is required. The test > even can be run in a virtual machine in case you would be worried about potential > impact of the test on the rest of the system. Your readme refers to kernel config options that don't even exist in the current kernel
