Received: by 2002:a05:6a10:6744:0:0:0:0 with SMTP id w4csp981733pxu; Wed, 7 Oct 2020 23:24:37 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxFXwfXREkvQqCWUQsh0iWdTpce3YV8xnQhn0Dqfae2FZLhS7xuZU9/98FR8i1QDQ1Gh3/7 X-Received: by 2002:aa7:d0d8:: with SMTP id u24mr7300021edo.349.1602138277710; Wed, 07 Oct 2020 23:24:37 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1602138277; cv=none; d=google.com; s=arc-20160816; b=DnynqQzk5acW9Cxm0J4EbY481m+gWVVQLIq3qCtX1yGU4My8cxO6cgnHhsy5iTMf27 sW1sbXRDlnOvzxNRzxDBgRZuTQUJ2dIaRl8FwI44iPFtex4EYwIQzjWb6BKAmdFehwnv KOhjeAaZRAUSFq9G+iurAAfP7V0R6YYL2rMFFKx8wqWJAi64ZkU2gRQo6GfR0XgifOFR 7873xF42/XvYkSL+9I0wfPKHbD0NJY/L/En9DcTfDh2DbQUvFkiE/6whz/E5NgOVCWbX 4UsPgfPjf+GcWNtFMpRtCqO3DD6MK573YWEUZNreNjRZpJuw2/v7mXdsoxyjPWk+IBSZ QV6g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:references:message-id:in-reply-to :subject:cc:to:from:date; bh=wYUnXG4FmOpqcnrAs9HGf9t9L6GGcR7v23uapDx9QII=; b=PrWpV4ebZGnUQvKbZxTMFirU4OmUFeCM2AFzCaibOEnZGETKYrW9OuiO4hA/8SbFFi LI1wSHD5TP5k/fer9UdxwkjSjvPinIxugu7LMUEdcaBQStDyv7xFH/W1QJYiM4S6n4hN GOcyFI0ExScs/Tl+CxTtbmHyrnJiszikn/mj8kTX2G5Y6ud3VYWuq5wHrvYC9kWmshhV nyG8scccTyVW7g/qrktD2UXFAGZh40maT0LK6wzFOYk7vnwqT6feEbT7tm1kqwoWzvn/ tm3msY6fcR7461RSATpX1Lm4k9OCukQS1QmMSnpxJmwMof7zizhLLzuHv3w2zQnNJUSr f/kQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id h23si3615675ejx.137.2020.10.07.23.24.14; Wed, 07 Oct 2020 23:24:37 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726371AbgJHGWz (ORCPT + 99 others); Thu, 8 Oct 2020 02:22:55 -0400 Received: from kvm5.telegraphics.com.au ([98.124.60.144]:47886 "EHLO kvm5.telegraphics.com.au" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726201AbgJHGWz (ORCPT ); Thu, 8 Oct 2020 02:22:55 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by kvm5.telegraphics.com.au (Postfix) with ESMTP id 47B522A040; Thu, 8 Oct 2020 02:22:51 -0400 (EDT) Date: Thu, 8 Oct 2020 17:22:50 +1100 (AEDT) From: Finn Thain To: Tony Asleson cc: Greg Kroah-Hartman , Christoph Hellwig , linux-scsi@vger.kernel.org, linux-block@vger.kernel.org, linux-ide@vger.kernel.org, Hannes Reinecke , pmladek@suse.com, David Lehman , 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 In-Reply-To: <72be0597-a3e2-bf7b-90b2-799d10fdf56c@redhat.com> Message-ID: References: <20200925161929.1136806-1-tasleson@redhat.com> <20200925161929.1136806-2-tasleson@redhat.com> <20200929175102.GA1613@infradead.org> <20200929180415.GA1400445@kroah.com> <20e220a6-4bde-2331-6e5e-24de39f9aa3b@redhat.com> <20200930073859.GA1509708@kroah.com> <20201001114832.GC2368232@kroah.com> <72be0597-a3e2-bf7b-90b2-799d10fdf56c@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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.