From: Finn Thain <fthain@telegraphics.com.au>
To: Tony Asleson <tasleson@redhat.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Christoph Hellwig <hch@infradead.org>,
linux-scsi@vger.kernel.org, linux-block@vger.kernel.org,
linux-ide@vger.kernel.org, Hannes Reinecke <hare@suse.de>,
pmladek@suse.com, David Lehman <dlehman@redhat.com>,
sergey.senozhatsky@gmail.com, jbaron@akamai.com,
James.Bottomley@HansenPartnership.com,
linux-kernel@vger.kernel.org, rafael@kernel.org,
martin.petersen@oracle.com, kbusch@kernel.org, axboe@fb.com,
sagi@grimberg.me, akpm@linux-foundation.org,
orson.zhai@unisoc.com, viro@zeniv.linux.org.uk
Subject: Re: [v5 01/12] struct device: Add function callback durable_name
Date: Thu, 8 Oct 2020 17:22:50 +1100 (AEDT) [thread overview]
Message-ID: <alpine.LNX.2.23.453.2010081721270.6@nippy.intranet> (raw)
In-Reply-To: <72be0597-a3e2-bf7b-90b2-799d10fdf56c@redhat.com>
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.
prev parent reply other threads:[~2020-10-08 6:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200925161929.1136806-1-tasleson@redhat.com>
[not found] ` <20200925161929.1136806-2-tasleson@redhat.com>
[not found] ` <20200929175102.GA1613@infradead.org>
[not found] ` <20200929180415.GA1400445@kroah.com>
[not found] ` <20e220a6-4bde-2331-6e5e-24de39f9aa3b@redhat.com>
[not found] ` <20200930073859.GA1509708@kroah.com>
[not found] ` <c6b031b8-f617-0580-52a5-26532da4ee03@redhat.com>
[not found] ` <20201001114832.GC2368232@kroah.com>
2020-10-07 20:10 ` Tony Asleson
2020-10-08 4:48 ` Greg Kroah-Hartman
2020-10-08 20:49 ` Martin K. Petersen
2020-10-08 5:54 ` Hannes Reinecke
2020-10-08 6:22 ` Finn Thain [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LNX.2.23.453.2010081721270.6@nippy.intranet \
--to=fthain@telegraphics.com.au \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@fb.com \
--cc=dlehman@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=hare@suse.de \
--cc=hch@infradead.org \
--cc=jbaron@akamai.com \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=orson.zhai@unisoc.com \
--cc=pmladek@suse.com \
--cc=rafael@kernel.org \
--cc=sagi@grimberg.me \
--cc=sergey.senozhatsky@gmail.com \
--cc=tasleson@redhat.com \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®