Missing InitialR2T key in response from target

[Tejas Vaykole <tejas.vaykole@xxxxxxxxxxxxxx>]

Hi ,

I'm looking for help in understanding how LIO handles key=value pair
during negotiation. The problem I'm experiencing now is that LIO seems to
ignore sending back 'InitialR2T' key=value pair.

For example, If am setting 'InitialR2T=Yes' using targetcli (output 
below) , and then trying to negotiate 'InitialR2T=No' .
I am getting back the key=value pair (attachment pcap InitialR2T_No )

-----targetcli ouput--------------
/> cd iscsi/iqn.2003-01.org.linux-iscsi.root.x8664:sn.4ba6ed0d62e7/tpg1/
/iscsi/iqn.20...ed0d62e7/tpg1> get parameter InitialR2T
InitialR2T=Yes
/iscsi/iqn.20...ed0d62e7/tpg1>
------------------------------------------

However, if I am setting 'InitialR2T=Yes' using targetcli and then 
trying to negotiate 'InitialR2T=Yes'
I am observing that LIO does *not* send back 'InitialR2T' key=value pair.
(attachment pcap InitialR2T_Yes)


As I understand, 'InitialR2T' is not a declarative key and therefore the 
target should respond with Key=value.

Is my understanding correct? Am I looking at an error ? Please confirm.

What more information do you want me to send ?

My Machine details :
1)
[root@root test_suite_iscsi]# uname -a
Linux root 3.9.10-100.fc17.x86_64 #1 SMP Sun Jul 14 01:31:27 UTC 2013 
x86_64 x86_64 x86_64 GNU/Linux

2)
[root@root test_suite_iscsi]# cat 
/sys/kernel/config/target/iscsi/lio_version
RisingTide Systems Linux-iSCSI Target v4.1.0-rc2

--
Thanks and regards.
Tejas Vaykole
Development Engineer.
Calsoft Inc.

Attachment: InitialR2T_No
Description: Binary data

Attachment: InitialR2T_Yes
Description: Binary data