Hi Nic, On 2/8/16, 9:25 PM, "Nicholas A. Bellinger" <nab@xxxxxxxxxxxxxxx> wrote: >Hi Himanshu, > >On Mon, 2016-02-08 at 23:27 +0000, Himanshu Madhani wrote: >> >> I am testing this series with with 4.5.0-rc2+ kernel and I am seeing >>issue >> where trying to trigger >> sg_reset with option of host/device/bus in loop at 120second interval >> causes call stack. At this point >> removing configuration hangs indefinitely. See attached dmesg output >>from >> my setup. >> > >Thanks alot for testing this. > >So It looks like we're still hitting a indefinite schedule() on >se_cmd->cmd_wait_comp once tcm_qla2xxx session disconnect/reconnect >occurs, after repeated explicit active I/O remote-port sg_resets. > >Does this trigger on the first tcm_qla2xxx session reconnect after >explicit remote-port sg_reset..? Are session reconnects actively being >triggered during the test..? > >To verify the latter for iscsi-target, I've been using a small patch to >trigger session reset from TMR kthread context in order to simulate the >I_T disconnects. Something like that would be useful for verifying with >tcm_qla2xxx too. > >That said, I'll be reproducing with tcm_qla2xxx ports this week, and >will enable various debug in a WIP branch for testing. Let me know if I can help in any way for testing/validating this series. > >Thank you, > >--nab >
<<attachment: winmail.dat>>
