Received: by 2002:a05:6a10:5bc5:0:0:0:0 with SMTP id os5csp1611976pxb; Mon, 11 Oct 2021 09:28:10 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyjbuP1gh9hRwFY7gf1+WUVk6XntjYXvLBbB4aUqEFOSyFCfrf5SctOvLxUtIW35FrCFgVl X-Received: by 2002:a50:cc03:: with SMTP id m3mr43435796edi.278.1633969689939; Mon, 11 Oct 2021 09:28:09 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1633969689; cv=none; d=google.com; s=arc-20160816; b=rahLQ8I/IHsnzAyXpBSg0fJ5vvu2+e0jMEewfbknZtFsOPOCbRMCWXIMBBqsF7AQ/W IL7eYCghdRw9BQSUpvcFem8bl4F/MiwzCMAG1vzp23Qg06jUrhjDZYGKgmuAHNB4y7Ux CFpBfrkf6raW5tWFmCaeKm7DWRM7noZIIuZ6MMDl9CciQ2OPO4YhoXShx0+U/b8koven hEmi6AliHNVsLPp6dSKTs38n782J00EjO22lS4IkpiPP+luUddI2xIpOpyv7P7fBKRl9 Pfuxz+GHoSZDXijs/llGAbV0dhbh4KTGEH5D84tZaGKwoV0biRiGSGZtoGj+UsX3jG5c sy2A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject; bh=quPJnR1ENDo8f3R6Lxeh0kIlt0ZBmOzgV9eFBdptpiU=; b=ke0Dh5mWZF608krLE3SW70j1yu7kp4sb0NV15RFpEfTPshkSOfWaMkzqnyFZ0Eawp3 MgF35BJq9ge+1QvcBal/gv2MnFPdetuwInxRTIT8JZ1cdm+ZuI6osd9w8/kdIRO4td0v j8kIT4Llg7GKqVcVogZfDHe9K/NbXPwnvRKxaOEko81CnteDqdEVcbOetq6EowiOGOsS NL2m97+5uziO+JKndpYFU/Pn/6lxdIDjM+Q+jaTH+7ycsCd5idaG6JP3fsMkdGXJI9kM c9rrqJwNX+nFJeUuli8MdV6gdVAEIVBojVe92M7H3m36qqUwe0fqNqH7w97bnC3G8gqa l7Bw== 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 z16si16436108edm.21.2021.10.11.09.27.46; Mon, 11 Oct 2021 09:28:09 -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 S236797AbhJKNKR (ORCPT + 99 others); Mon, 11 Oct 2021 09:10:17 -0400 Received: from mx3.molgen.mpg.de ([141.14.17.11]:42625 "EHLO mx1.molgen.mpg.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S235410AbhJKNKQ (ORCPT ); Mon, 11 Oct 2021 09:10:16 -0400 Received: from [192.168.0.7] (ip5f5aef5a.dynamic.kabel-deutschland.de [95.90.239.90]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) (Authenticated sender: pmenzel) by mx.molgen.mpg.de (Postfix) with ESMTPSA id A062561E5FE33; Mon, 11 Oct 2021 15:08:15 +0200 (CEST) Subject: Re: SK hynix BC511: warning: nvme nvme0: missing or invalid SUBNQN field. To: Keith Busch Cc: Jens Axboe , Christoph Hellwig , Sagi Grimberg , linux-nvme@lists.infradead.org, LKML , Dell.Client.Kernel@dell.com References: <67f74c8e-9d5e-22a1-f1c2-a4284b07ba56@molgen.mpg.de> <20210817161638.GC223727@dhcp-10-100-145-180.wdc.com> <20210817170222.GA224912@dhcp-10-100-145-180.wdc.com> From: Paul Menzel Message-ID: Date: Mon, 11 Oct 2021 15:08:15 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0 MIME-Version: 1.0 In-Reply-To: <20210817170222.GA224912@dhcp-10-100-145-180.wdc.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Dear Keith, Am 17.08.21 um 19:02 schrieb Keith Busch: > On Tue, Aug 17, 2021 at 06:53:15PM +0200, Paul Menzel wrote: >> [cc: +Dell.Client.Kernel@dell.com as it’s a Dell device] >> Am 17.08.21 um 18:16 schrieb Keith Busch: >>> On Tue, Aug 17, 2021 at 05:10:40PM +0200, Paul Menzel wrote: >>>> On a Dell OptiPlex 7780 AIO/04G47W (BIOS 1.6.3 03/08/2021) Linux 5.10.47 >>>> shows the warning below: >>>> >>>> $ dmesg | grep nvme >>>> [ 3.015392] nvme 0000:02:00.0: platform quirk: setting simple suspend >>>> [ 3.021861] nvme nvme0: pci function 0000:02:00.0 >>>> [ 3.026593] ahci 0000:00:17.0: version 3.0 >>>> [ 3.026922] ahci 0000:00:17.0: AHCI 0001.0301 32 slots 1 ports 6 Gbps 0x1 impl SATA mode >>>> [ 3.035020] ahci 0000:00:17.0: flags: 64bit ncq sntf pm clo only pio slum part ems deso sadm sds apst >>>> [ 3.035219] nvme nvme0: missing or invalid SUBNQN field. >>>> [ 3.044518] scsi host0: ahci >>>> [ 3.051632] nvme nvme0: 12/0/0 default/read/poll queues >>>> [ 3.052590] ata1: SATA max UDMA/133 abar m2048@0xd1339000 port 0xd1339100 irq 125 >>>> [ 3.058538] nvme0n1: p1 p2 p3 >>>> >>>> Should it be added to the quirk list in `drivers/nvme/host/pci.c` or is it a >>>> real issues, the manufacturer should fix? If so, do you have SK Hynix >>>> contacts? >>> >>> It would be great if device makers would be spec compliant, but the >>> driver will continue to work with the device the same whether you add >>> the quirk or not. >> >> Could you please point me to the NVMe specification section, so I can refer >> to it, when contacting the manufacturer? > > In the section for "Identify Controller Data Structure" (section > 5.17.2.1, figure 257 in spec version 2.0), the NQN definition says: > > "Support for this field is mandatory if the controller supports revision > 1.2.1 or later" > > The driver does confirm the controller's reported revision meets this > requirement before emitting the warning. The Dell support came back to me, and said, that Hynix refuses to publish a fixed firmware unless I show them a use case, where I need that field. Can somebody think of a use case, and why this field was made mandatory in the specification? Kind regards, Paul