From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 0A68F340DB8 for ; Thu, 16 Apr 2026 22:11:55 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1776377516; cv=none; b=HAZeE6SGOQkYdtQDe3dF9DC+8OEPcQdSh+po+hYH4GISadloOAcgNUnez2ke/jW8yQpeuPtT30gfblySnmhEe/35Gk35jRRpel96CsqXH2YCrrsXeBH4LwU6x2M27G3VRHY9ODOj5VntGyvaYwjOjOtb/vEGfulizufTXE85WpA= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1776377516; c=relaxed/simple; bh=KyWB9ycvHqkmpmposSJtxAzlyFaOpjGf/DPS/R71W6Q=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=JYf+DC5Wb6xVMgWbnpAkjqpbWyUomjvFB2gZGlSg4CNW0QRDl9bLvZq91bvPQqU0XzlsE1y9ZItKunO/VXLFizmoO3EWJjqKndNBelB+PX17HhVwMjVYXb62jVT4ZQztW9VsN55+kxynv2nj1a+teUVC1mQPXIlc/CILxsacyRU= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=tyYDlTI/; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="tyYDlTI/" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 52D34C2BCAF; Thu, 16 Apr 2026 22:11:55 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1776377515; bh=KyWB9ycvHqkmpmposSJtxAzlyFaOpjGf/DPS/R71W6Q=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=tyYDlTI/ahHVBH3cT7RBDmQOh+9tB6lR0gXv+8TBxYY7XSwlOiQHSrHVQK1SPNVZu lAdeOs+E5UoWhY144hpS8F9EkppzizxZrPercOtC/+QJXJ1QIysGZGMFKX4ypbSUHF PqC1RivU/0e2zTQ5RhMLHjfcoDxn/C+xx46ASWS+7e0iRu4mQPujnlMQR5dcP2zAkR ypxucjtsmCP6Qz9vz5SlGTtW8X/iwSaOa4AnvqZ1r+LloDWyT5jIkWjoUAwZkHu4TM AtVVcLp3kge97eZn1QYTQCCMqk/PlPudsiyvv5sHoMzjzGr8/ua57wMKXhRILqumVu TpumQ5ep887CQ== Date: Thu, 16 Apr 2026 16:11:53 -0600 From: Keith Busch To: Tao Jiang Cc: linux-nvme@lists.infradead.org, axboe@kernel.dk, hch@lst.de, sagi@grimberg.me, linux-kernel@vger.kernel.org Subject: Re: [PATCH] nvme-pci: add quirk for Memblaze Pblaze5 (0x1c5f:0x0555) Message-ID: References: <1776274035-1604-1-git-send-email-tanroame.kyle@gmail.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1776274035-1604-1-git-send-email-tanroame.kyle@gmail.com> On Thu, Apr 16, 2026 at 01:27:15AM +0800, Tao Jiang wrote: > The Memblaze Pblaze5 NVMe device (PCI ID 0x1c5f:0x0555) > is detected as a controller on recent kernels (tested on 5.15.85 > and 6.8.4), but no namespace is exposed. > > Tools like lsblk and fdisk do not report any block device. > > dmesg shows: > nvme nvme0: missing or invalid SUBNQN field. > > The device works correctly on older kernels (e.g. 4.19), suggesting > a compatibility issue with newer namespace handling. > > This indicates the device does not properly support the > Namespace Descriptor List feature. > > Applying NVME_QUIRK_NO_NS_DESC_LIST allows the namespace to be > discovered correctly. Thanks, applied to nvme-7.1.