From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (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 CBC9317BB21 for ; Tue, 25 Aug 2026 00:56:11 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1787619372; cv=none; b=f5D9sAqTTy73/W6AF2ms4UwuN+5nAzG7PUHb0EwqEqode3CQ7m7bcCy5sugNDMptCHCeMNlgK4ydhIrxjMPlQ4eqzawH5ww2qSxvdiR+dPdGzXzHxEusrhvxpN2A0O4sLQ3RoOSOq3Ir7Syq4JUuHbX7U2XEAKh3hQKWoAf33J4= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1787619372; c=relaxed/simple; bh=NBQY4C3RIx/vod90X+9ZXncd+BU8tdkFzfYAxnfcqSY=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=cedGChQz+SjwNSnvPo9aLGusaMCoyJz4V7HH2NFisAcCrYcvVAvCssuGpyH4yh/q7LWDXiK6SNLITrfUaN5flfuiPqenSqL9/uM/i71s/74XfZHjd4X5kl3CSbuJVHMhIIVYU6kIIb5RsBT9VzBhlwLmmRbRvlcMtiAe2dyRpuQ= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=NPLfckCL; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="NPLfckCL" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 3A40B1F000E9; Tue, 25 Aug 2026 00:56:11 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1787619371; bh=9mrOq5pNWRQKbPuwbSb5LK9W7IPmqYibvjgO/RM65Q4=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=NPLfckCLQaXfHbqkRFWFAiTnDhqLS9akLW7M3/LDalnh+j3XMUJcxvtCaZEzIP6wz 7c4UcXCbA3nswl4Aby/5I1esorynKja7DmodMICZBymVQN8eW0+7wi2zOifBemXfa3 wBjzWgTc5Lhx0vTWMwpvr2kwn5r1+0bD8JYoKE6WuXluayZGI8UAUdNTlFRkm0QInn JrV0+w3/yxr4uy5dO4dcYrLvXacVeCw9XsAZ39Qo7Sw5xjDT8tyVtTVT8MyapsSNP1 InHDyAnQzXkfe2NTZTAMTQnBbHkdSO04lNQ1/N/m506F1c+Qr37dH7EyzroInKhYSu WX/2nNoPrzHzQ== Date: Mon, 24 Aug 2026 18:56:09 -0600 From: Keith Busch To: Mohamed Khalfella Cc: Jens Axboe , Christoph Hellwig , Sagi Grimberg , Chaitanya Kulkarni , linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 1/2] nvme: print namespace IDs as unsigned 32bit value Message-ID: References: <20260821230310.3937527-1-mkhalfella@purestorage.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: <20260821230310.3937527-1-mkhalfella@purestorage.com> On Fri, Aug 21, 2026 at 04:03:09PM -0700, Mohamed Khalfella wrote: > NSIDs are 32-bit unsigned values, but a number of log messages print > them with %d. An NSID larger than 0x7fffffff is rendered as a negative > number, which is confusing in the kernel log and makes the message hard > to correlate with the namespace it talks about. Sparse NSID spaces > where high NSIDs are common are the most likely to hit this. > > The nsid sysfs attribute has the same problem, and there it is worse > because userspace parses the value. Thanks, applied to nvme-7.3.