linux-kernel - Re: [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-prev] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 12 Jul 2021 10:34:01 +0100
From:   Stefan Hajnoczi <stefanha@...hat.com>
To:     Wenchao Hao <haowenchao@...wei.com>
Cc:     "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>,
        linux-scsi@...r.kernel.org,
        virtualization@...ts.linux-foundation.org,
        linux-kernel@...r.kernel.org,
        Zhiqiang Liu <liuzhiqiang26@...wei.com>,
        Wu Bo <wubo40@...wei.com>, linfeilong@...wei.com,
        yuzhanzhan@...wei.com
Subject: Re: [bug report]scsi: drive letter drift problem

On Mon, Jul 12, 2021 at 12:47:05PM +0800, Wenchao Hao wrote:
> 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?

Is there a stable ID that you can use in /dev/disk/by-*?

Stefan

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)