On Thu, 2017-06-01 at 20:53 -0700, Nicholas A. Bellinger wrote: > On Thu, 2017-06-01 at 15:35 +0000, bugzilla-daemon@xxxxxxxxxxxxxxxxxxx > wrote: > > https://bugzilla.kernel.org/show_bug.cgi?id=195963 > > [ ... ] > > Call Trace: > > refcount_dec_and_test+0x11/0x20 > > target_put_sess_cmd+0x14/0x30 [target_core_mod] > > core_tmr_abort_task+0x140/0x1b0 [target_core_mod] > > target_tmr_work+0x116/0x130 [target_core_mod] > > process_one_work+0x1ca/0x3f0 > > worker_thread+0x49/0x3b0 > > kthread+0x109/0x140 > > ret_from_fork+0x2a/0x40 > > Well, I'm not able to reproduce on target-pending/master with > iscsi-test-cu --test=ALL --dataloss, or with the debug code to force > ABORT_TASK + session shutdown to occur. > > I assume that MNC wasn't able to reproduce either on > target-pending/master either, as he's been testing the same code-path to > verify: > > commit 25cdda95fda78d22d44157da15aa7ea34be3c804 > Author: Nicholas Bellinger <nab@xxxxxxxxxxxxxxx> > Date: Wed May 24 21:47:09 2017 -0700 > > iscsi-target: Fix initial login PDU asynchronous socket close OOPs > > So are you sure you're not running with more of your out-of-tree code..? > > If not, what are the steps to reproduce..? Hello Nic, Yes, I'm sure that my pending patches were not responsible for triggering this. After I encountered this warning for the first time I switched to the git branch with Linus' tree, double checked there were no local modifications, ran git clean -f -d -x, rebuilt the kernel, rebooted and repeated my test. The command I ran to trigger this issue is as follows: for ((i=1;i<=2;i++)); do time ./iscsi-test-cu --dataloss --allow-sanitize iscsi://127.0.0.1/tgt1/$i iscsi://127.0.0.1/tgt2/$i; done libiscsi was granted access to both tgt1 and tgt2. LUN 1 uses the FILEIO backend while LUN 2 uses the IBLOCK backend driver. Bart.-- To unsubscribe from this list: send the line "unsubscribe target-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
