Received: by 2002:a25:868d:0:0:0:0:0 with SMTP id z13csp2993968ybk; Mon, 18 May 2020 13:04:41 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyIu0It1psw0h+Xs31HTx1zWn74DiaJ336hy77LYovwh5QgYnrOfIBflPpj8XMt6nQjFxPH X-Received: by 2002:a05:6402:1cb6:: with SMTP id cz22mr14320629edb.86.1589832281378; Mon, 18 May 2020 13:04:41 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1589832281; cv=none; d=google.com; s=arc-20160816; b=g5bleKLN1m0IRJEBai0NzQ77Pl1BhJNY4r+ZHiVui0E3C7+v40Xuvd38SDYorLAhG7 cyXF/FdPxACnXTMEW5S1jfaYTIRkaJqnsJCI/6FI/txEwhrMfn2WubquRwvGjdSduitO xnqFteQLoOnnoIouAKWh5Pit9TOjsXQQqf6usge2Tc4yGxMtmIXIGisxFRY/jXJcm5ZG P+rPp94F5illCKRYqVCKmOzsuRUqlAbzXeH1sxr9S+spSLNe+Ga00h2Xac/hHmUnBdS7 f2Z8SyCk5d/g7Ixlpb8l5gwgbBOc5QHT99IczenpfQlvez9lXKvaVlrWO2sZFD1F884/ YYwQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature; bh=tG4NW0XrpKeglSu1M3LhtqURiiCPd6FFbzkD+elHvV4=; b=Ufa2S7H4AdDBhvelwnPz09x9vlnPMmS/u36WjUOBZ+J/5S25mSvjFmIHXQzv7D1/BX U7Yne/Lq5fQZbdfBflo/uSeRzRP/FkIhJruugWTF04/DfG15IrVWW4W94JWO2wnwiMfN TRN0RVeRK8vg/k+VjNZBjXGyY5m/Q0VIlE/5V7iKFq04YJ/Y74f3dDHv7JQedojQfJOb Lhy/xwwtnMcmFxASk8CnZwB7489LQPXJCoc3j7kvGOJKKN5xOjPLUKTm1O4w52/d+Lso GzsH7LZC++vkRo+p3BNVUV3cS9MYVbd7bvJVujXowQu/4/KMmn8YF3iVn68noUXVfPaB mODw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=hgKqhTbe; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id e1si6787418ejr.438.2020.05.18.13.04.18; Mon, 18 May 2020 13:04:41 -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; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=hgKqhTbe; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728345AbgERTk1 (ORCPT + 99 others); Mon, 18 May 2020 15:40:27 -0400 Received: from us-smtp-delivery-1.mimecast.com ([205.139.110.120]:45787 "EHLO us-smtp-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1728333AbgERTk1 (ORCPT ); Mon, 18 May 2020 15:40:27 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1589830826; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=tG4NW0XrpKeglSu1M3LhtqURiiCPd6FFbzkD+elHvV4=; b=hgKqhTbe8oJUr8lG6xaOpKDqS5ubTWgo5iPHkqUXu6haE/drB72AdYwlk27tAJQ4AVlzup xRRE2CrW6rGpwo2zb8nSiSp4scy66KvOmTxakE3pFkcYQphXr3Z+9XyDMTmiCF/Y6x6nuw 9K6LfuA79In2ZHzhzUWuYBZdde1PKIo= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-396-U05quBLcPiW7lZDGRiusAg-1; Mon, 18 May 2020 15:40:24 -0400 X-MC-Unique: U05quBLcPiW7lZDGRiusAg-1 Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 90C0E835B40; Mon, 18 May 2020 19:40:23 +0000 (UTC) Received: from [10.10.118.151] (ovpn-118-151.rdu2.redhat.com [10.10.118.151]) by smtp.corp.redhat.com (Postfix) with ESMTP id E9ED919634; Mon, 18 May 2020 19:40:22 +0000 (UTC) Subject: Re: [PATCH v1 target] target: Add initiatorname to NON_EXISTENT_LUN error To: Lance Digby , martin.petersen@oracle.com Cc: linux-scsi@vger.kernel.org, target-devel@vger.kernel.org, linux-kernel@vger.kernel.org References: <9b13bb2e1f52f1792cd81850ee95bf3781bb5363.1589759816.git.lance.digby@gmail.com> From: Mike Christie Message-ID: Date: Mon, 18 May 2020 14:40:22 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.5.0 MIME-Version: 1.0 In-Reply-To: <9b13bb2e1f52f1792cd81850ee95bf3781bb5363.1589759816.git.lance.digby@gmail.com> Content-Type: text/plain; charset=windows-1252 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.79 on 10.5.11.11 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 5/17/20 8:02 PM, Lance Digby wrote: > The NON_EXISTENT_LUN error can be written without an error condition > on the initiator responsible. Adding the initiatorname to this message > will reduce the effort required to fix this when many initiators are > supported by a target. > > This version ensures the initiator name is also printed on the same > message in transport_lookup_tmr_lun for consistency. > Reviewed-by: Mike Christie