On Mon, 2011-11-28 at 17:14 +0800, Jim Barber wrote: > > Just to be clear which branch did you use? > > > > What was the git revision of the head you built? > > I'll admit that I'm a total beginner when it comes to git and just learnt enough to pull this project. > I followed some instructions somewhere on the http://linux-iscsi.org web site which said to do something like: > > git checkout --track -b tcm_qla2xxx origin/tcm_qla2xxx > git pull origin tcm_qla2xxx > > But that didn't work so well, so I did a: > > git ls-remote > > Which showed me that there was a qla_tgt-3.3 branch. > So I did: > > git checkout --track -b qla_tgt-3.3 origin/qla_tgt-3.3 > git pull origin qla_tgt-3.3 > > A 'git branch' shows: > > # git branch > master > * qla_tgt-3.3 > > I'm not sure how to answer what git revision of the head I built... > > A 'git show' has the following output: > > commit 401b01afba24797e888ff88d8c27d3bfe3116697 > Author: Nicholas Bellinger <nab@xxxxxxxxxxxxxxx> > Date: Fri Nov 18 16:45:15 2011 -0800 > > qla2xxx: Remove duplicate assignments from qla_tgt_do_work > > This patch removes duplicate assignments for qla_tgt_cmd related to > descriptor setup in qla_tgt_do_work(). The original assignments for > these values has already done in qla_tgt_handle_cmd_for_atio() before > dispatch to workqueue process context. > > Signed-off-by: Nicholas Bellinger <nab@xxxxxxxxxxxxxxx> > Hello Jim, Thank you for the detailed bug-report with lio-core.git code. I'm pretty certain this is going to be fallout related the recent qla_tgt-3.3 cleanups to remove qla_tgt_cmd->locked_rsp in qla_target.c check condition exception path. I think there is enough information in your original logs to reproduce the issue on my side, and will go ahead and Cc' you directly when we have a bugfix patch to verify on your end. Thanks for testing! --nab -- 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
