Comment 6 for bug 1636467

>any suggestions here about getting this issue fixed into lsscsi utility

Ah, yeah, it can sometimes take a bit of persistence at getting a maintainer's attention. Still, its the right thing to do to continue to pursue that path as wanting to ensure there aren't side effects you have not thought of. I'd suggest you also try posting patches to the linux-scsi mailing list as the maintainer appears to be active in that forum.

However, it doesn't seem terrible for us to carry an Ubuntu patch for this at least temporarily with the assumption that you'll keep working to get upstreamed so we can drop such patch going forward.

 >> we (IBM) don't use Debian for any internal testing. In case upstream maintainer follows Debian bugs for lsscsi utlity

FWIW, its pretty easy to set up a LXD container or VM with docker and reproduce this bug, and then use the 'reportbug' utility. I'd do so, but I lack the hardware to validate your bug.