On 10/03/16 20:56, Chris Boot wrote: > On 05/03/16 09:33, Nicholas A. Bellinger wrote: >> On Sat, 2016-03-05 at 08:45 +0000, Chris Boot wrote: >>> Are these in linux-next or another branch somewhere I can easily clone >>> them from? >> >> The patch series is in target-pending/for-next. > > Hi Nic, > > I've just managed to resurrect a test rig for this (the hardware I had > for it has stopped being usable, yay!), and my initial testing shows the > updated code panics on the first submitted IO. So this isn't the first IO, it's exactly the 2nd IO. I'm hitting BUG_ON(se_cmd->se_tfo || se_cmd->se_sess) in target_submit_cmd_map_sgls(). I'm assuming the se_cmd is being reused due to percpu ida allocator, and the code must be missing something to clean up the se_cmd sufficiently once we're done with it. At this point I'm out of my depth going through the target core, so I'd appreciate some pointers to get any further! Thanks, Chris -- Chris Boot bootc@xxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
