linux-kernel - Re: [v5 01/12] struct device: Add function callback durable

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]

Message-ID: <alpine.LNX.2.23.453.2010081721270.6@nippy.intranet>
Date:   Thu, 8 Oct 2020 17:22:50 +1100 (AEDT)
From:   Finn Thain <fthain@...egraphics.com.au>
To:     Tony Asleson <tasleson@...hat.com>
cc:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Christoph Hellwig <hch@...radead.org>,
        linux-scsi@...r.kernel.org, linux-block@...r.kernel.org,
        linux-ide@...r.kernel.org, Hannes Reinecke <hare@...e.de>,
        pmladek@...e.com, David Lehman <dlehman@...hat.com>,
        sergey.senozhatsky@...il.com, jbaron@...mai.com,
        James.Bottomley@...senPartnership.com,
        linux-kernel@...r.kernel.org, rafael@...nel.org,
        martin.petersen@...cle.com, kbusch@...nel.org, axboe@...com,
        sagi@...mberg.me, akpm@...ux-foundation.org, orson.zhai@...soc.com,
        viro@...iv.linux.org.uk
Subject: Re: [v5 01/12] struct device: Add function callback durable_name

On Wed, 7 Oct 2020, Tony Asleson wrote:

> The log information is not helpful without the information to correlate 
> to the actual device.

Log messages that associate one entity with another can be generated 
whenever such an association comes into existence, which is probably when 
devices get probed.

E.g. a host:channel:target:lun identifier gets associated with a block 
device name by the dev_printk() calls in sd_probe():

[    3.600000] sd 0:0:0:0: [sda] Attached SCSI disk

BTW, if you think of {"0:0:0:0","sda"} as a row in some normalized table 
and squint a bit, this problem is not unlike the replication of database 
tables over a message queue.