• Daniel Verkamp's avatar
    nvmet: fix KATO offset in Set Features · 6c73f949
    Daniel Verkamp authored
    The Set Features implementation for Keep Alive Timer was using the wrong
    structure when retrieving the KATO value; it was treating the Set
    Features command as a Property Set command.
    
    The NVMe spec defines the Keep Alive Timer feature as having one input
    in CDW11 (4 bytes at offset 44 in the command) whereas the code was
    reading 8 bytes at offset 48.
    
    Since the Linux NVMe over Fabrics host never sets this feature, this
    code has presumably never been tested.
    Signed-off-by: default avatarDaniel Verkamp <daniel.verkamp@intel.com>
    Signed-off-by: default avatarChristoph Hellwig <hch@lst.de>
    6c73f949
admin-cmd.c 13.9 KB