SORT BY:

LIST ORDER
THREAD
AUTHOR
SUBJECT


SEARCH

IPS HOME


    [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

    RE: iSCSI ABORT TASK RefCmdSN question



    > Suppose an iSCSI target receives an ABORT TASK Task Management Function
    that
    > does not refer to a valid task (i.e. the Referenced Task Tag does not
    match
    > any task at the target) but the CmdSN is inside the valid window and
    matches
    > a non-immediate command that has not yet been delivered for execution.
    For
    > example,
    > 
    > Target's ExpCmdSN is 10.
    > Target has a queued non-immediate command with CmdSN 11 and 
    > Initiator Task Tag of 55 which has not been delivered for execution
    > because the target is waiting for a non-immediate command with CmdSN 10
    > first.  Target receives an immediate ABORT TASK Task Management Function
    > with Referenced Task Tag of 66 and RefCmdSN of 11.
    
    This is an error.  The initiator has violated the following MUST:
    
    9.5.5  RefCmdSN
    
       For the ABORT TASK function, initiators MUST always set this to the 
       CmdSN of the task identified by the Referenced Task Tag field. Tar-
       gets must use this field as described in section 9.6.1 when the task 
       identified by the Referenced Task Tag field is not with the target.
    
    A Reject PDU with Reason 0x09 will do nicely to tell the Initiator that
    it screwed up.  Processing an erroneous task management function
    request by trying to infer what the initiator might have intended is
    not a good idea.
    
    Thanks,
    --David
    ---------------------------------------------------
    David L. Black, Senior Technologist
    EMC Corporation, 42 South St., Hopkinton, MA  01748
    +1 (508) 249-6449            FAX: +1 (508) 497-8018
    black_david@emc.com       Mobile: +1 (978) 394-7754
    ---------------------------------------------------
    
    
    


Home

Last updated: Fri Aug 30 14:18:58 2002
11728 messages in chronological order