linux-kernel - [bug report]scsi: drive letter drift problem

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-next>] [day] [month] [year] [list]

Date:   Mon, 12 Jul 2021 12:47:05 +0800
From:   Wenchao Hao <haowenchao@...wei.com>
To:     "James E.J. Bottomley" <jejb@...ux.ibm.com>,
        "Martin K. Petersen" <martin.petersen@...cle.com>,
        "Michael S. Tsirkin" <mst@...hat.com>,
        "Jason Wang" <jasowang@...hat.com>,
        Paolo Bonzini <pbonzini@...hat.com>,
        "Stefan Hajnoczi" <stefanha@...hat.com>,
        <linux-scsi@...r.kernel.org>,
        <virtualization@...ts.linux-foundation.org>,
        <linux-kernel@...r.kernel.org>
CC:     Zhiqiang Liu <liuzhiqiang26@...wei.com>, Wu Bo <wubo40@...wei.com>,
        <linfeilong@...wei.com>, <yuzhanzhan@...wei.com>,
        <haowenchao@...wei.com>
Subject: [bug report]scsi: drive letter drift problem

We deploy two SCSI disk in one SCSI host(virtio-scsi bus) for one 
machine, whose ids are [0:0:0:0] and [0:0:1:0].

Mostly, the device letter are assigned as following after reboot:
[0:0:0:0] --> sda
[0:0:1:0] --> sdb

While in rare cases, the device letter shown as following:
[0:0:0:0] --> sdb
[0:0:1:0] --> sda

Could we guarantee "sda" is assigned to [0:0:0:0] and "sdb" is assigned 
to [0:0:1:0] or not?
If we can, then how?