Hello Zhu, The test I ran is as follows: * Clone the linux-next repository (https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git) * Use label next-20180329: git checkout next-20180329 -b linux-next-20180329 * Configure the kernel as explained on https://github.com/bvanassche/srp-test. * Build and install the linux-next kernel in a virtual machine. * Boot the linux-next kernel. * Run the srp-test software as follows: srp-test/run_tests -c -d -r 10 * Shut down the virtual machine by running the poweroff command. During shutdown the rxe driver crashes. That crash does not occur with kernel v4.16-rc7. Additionally, that crash does not occur if I run the srp-test software against the mlx4_ib driver. So I think this crash indicates a recently introduced regression in the rdma_rxe driver. Can you have a look? Thanks, Bart. ------------[ cut here ]------------ kernel BUG at mm/slub.c:296! invalid opcode: 0000 [#1] SMP PTI CPU: 3 PID: 30 Comm: ksoftirqd/3 Not tainted 4.16.0-rc7-next-20180329-dbg+ #1 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.0.0-prebuilt.qemu-project.org 04/01/2014 RIP: 0010:kfree+0x2c3/0x2e0 Call Trace: skb_free_head+0x21/0x30 skb_release_data+0x111/0x170 skb_release_all+0x24/0x30 kfree_skb+0x4d/0x150 rxe_requester+0xa7f/0x11a0 [rdma_rxe] rxe_do_task+0x87/0x100 [rdma_rxe] tasklet_action_common.isra.17+0x81/0x1e0 tasklet_action+0x22/0x30 __do_softirq+0xcf/0x4b1 run_ksoftirqd+0x33/0x50 smpboot_thread_fn+0xfc/0x170 kthread+0x121/0x140 ret_from_fork+0x3a/0x50 RIP: kfree+0x2c3/0x2e0 RSP: ffffac690041fc68 ---[ end trace 03df278c17f7be7d ]--- Kernel panic - not syncing: Fatal exception in interrupt Kernel Offset: 0x3c000000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff) ---[ end Kernel panic - not syncing: Fatal exception in interrupt ]--- ��.n��������+%������w��{.n�����{���fk��ܨ}���Ơz�j:+v�����w����ޙ��&�)ߡ�a����z�ޗ���ݢj��w�f
