linux-kernel - Re: [PATCH v1 target] target: Add initiatorname to NON_EXISTENT

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <158994171818.20861.13529776753176885593.b4-ty@oracle.com>
Date:   Tue, 19 May 2020 22:30:07 -0400
From:   "Martin K. Petersen" <martin.petersen@...cle.com>
To:     mchristi@...hat.com, Lance Digby <lance.digby@...il.com>
Cc:     "Martin K . Petersen" <martin.petersen@...cle.com>,
        target-devel@...r.kernel.org, linux-scsi@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1 target] target: Add initiatorname to NON_EXISTENT_LUN error

On Mon, 18 May 2020 11:02:16 +1000, Lance Digby wrote:

> The NON_EXISTENT_LUN error can be written without an error condition
> on the initiator responsible. Adding the initiatorname to this message
> will reduce the effort required to fix this when many initiators are
> supported by a target.
> 
> This version ensures the initiator name is also printed on the same
> message in transport_lookup_tmr_lun for consistency.

Applied to 5.8/scsi-queue, thanks!

[1/1] scsi: target: core: Add initiatorname to NON_EXISTENT_LUN error
      https://git.kernel.org/mkp/scsi/c/5482d56bfedf

-- 
Martin K. Petersen	Oracle Linux Engineering