#182 NOP-IN from target handling 4.0.2

open
nobody
None
5
2005-09-13
2005-09-13
Anonymous
No

The first 2 bits in NOP-IN command from target should
not be interpreted, they are optional bits. The bug is
when Linux initiator receive these NOP-IN command, it
uses these field, so instead of being 0x20, it interprets
as 0xe0 [ethereal interprets it correctly as NOP-IN
command]

Discussion

  • Logged In: NO

    From sect 10 of the RFC it says that those bits should be
    zered too right? I guess both the initiator and target are
    bad. Will fix.

     
  • Logged In: NO

    oh yeah what target is doing this btw?