All of lore.kernel.org
 help / color / mirror / Atom feed
From: "MINOURA Makoto / 箕浦 真" <minoura@valinux.co.jp>
To: stgt@vger.kernel.org
Subject: ExpCmdSn and MaxCmdSn in ISCSI_OP_R2T
Date: Fri, 23 Jan 2015 09:08:33 +0900	[thread overview]
Message-ID: <kk5iofyfjem.fsf@brer.local.valinux.co.jp> (raw)


tgtd does not send ExpCmdSn and MaxCmdSn with OP_R2T (Ready
To Transfer) operations.  Is this behaviour correct?

At least Linux (RHEL6.2) initiators take 0 MaxCmdSn value
and get confused.


Frame 1498: 114 bytes on wire (912 bits), 114 bytes captured (912 bits)
Ethernet II, Src: XXXX, Dst: XXXX
Internet Protocol Version 4, Src: 172.17.105.40 (172.17.105.40), Dst: 172.17.105.39 (172.17.105.39)
Transmission Control Protocol, Src Port: iscsi-target (3260), Dst Port: 59099 (59099), Seq: 1620029, Ack: 42313, Len: 48
iSCSI (Ready To Transfer)
    Opcode: Ready To Transfer (0x31)
    TotalAHSLength: 0x00
    DataSegmentLength: 0x00000000
    LUN: 1 (Single Level LUN Structure)
        00.. .... = Address Mode: Single Level LUN Structure (0)
        ..00 0000 = BUS: 0
        LUN: 1
    InitiatorTaskTag: 0x0b000000
    TargetTransferTag: 0x9077e700
    StatSN: 0x0000017d
    ExpCmdSN: 0x00000000                        !!!
    MaxCmdSN: 0x00000000                        !!!
    R2TSN: 0x00000000
    BufferOffset: 0x00002000
    DesiredDataLength: 0x00000200


iscsi_r2t_build() does not fill rsp->exp_cmdsn and rsp->max_cmdsn,
while iscsi_cmd_rsp_build() and iscsi_data_rsp_build() does.

-- 
Minoura Makoto <minoura@valinux.co.jp>

             reply	other threads:[~2015-01-23  0:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-23  0:08 MINOURA Makoto / 箕浦 真 [this message]
2015-01-26  3:49 ` ExpCmdSn and MaxCmdSn in ISCSI_OP_R2T MINOURA Makoto / 箕浦 真
2015-01-26  3:58   ` FUJITA Tomonori
2015-01-26  6:53     ` MINOURA Makoto / 箕浦 真

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=kk5iofyfjem.fsf@brer.local.valinux.co.jp \
    --to=minoura@valinux.co.jp \
    --cc=stgt@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.