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 A3C183321A2 for ; Mon, 20 Apr 2026 16:31:47 +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=1776702707; cv=none; b=T3//GNwtL2kX8hkLOkoxAvct5r9QxBsCqdqBTeLEqNmgwNcRJcJAH03B1wSxg1ieJvrUabYXxNqnzcS8edwjT81C3bBtELdP1WvOjqgGuGFWXQstchmTxwgMsvHVHGvfl9FfwY6chCuSWLUZgtkM7qQSIwIVkVf8HrX5Cu6SSms= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1776702707; c=relaxed/simple; bh=VBsLVBVRE4nyBy3Wpg8Yd3gtZ2HMfPTicIZv9PaDDDc=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=JV6ZFnb5cnhYtT6CcuCv2+ioX8l94CpVeFqmASSwAlcTiaVvAM5T3TlNbWvc42XM7/XefxRmImNhV2b0g7oNPj7nF7k08batmedNWLNRzf2vaJlMJCcVLuKfptcytjH1cg3ZTI2SUg9mizO07Rw4Af8mWtdWimyqNWM5i202xmU= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=TGA6Tz8l; 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="TGA6Tz8l" Received: by smtp.kernel.org (Postfix) with ESMTPSA id D3490C19425; Mon, 20 Apr 2026 16:31:46 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1776702707; bh=VBsLVBVRE4nyBy3Wpg8Yd3gtZ2HMfPTicIZv9PaDDDc=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=TGA6Tz8l+Efaeu3PJg1QUD1kEyP0pskaKjsXfZorH4bGmAxJLIH2zOKijqblg1TOL DX86YeoXeVAAuno1xtCUa+hX6mwgJ+YVXKzw0m9BcIKPt1pyTg41o/wqAk/8Ie9JoK Hvwq/erp3kL7EXCLegrh0GvCoIGmAkqC/fU//EjPBD0F4ol5DyfFekQp36qxEEi7km UzhKrXyHFacoQ02m7UBI2CLAbmwpDH6haTfHAK21UsRYZUiWoHBI4thDNn3gZaiVal szvFW4sWzg2IJwTZDQ6IL57acIcsaEWg1WRtHHNj6mtpWYqojQLa2zGIhxypWS4Bxl +eWSrF/VPp7Hg== Date: Mon, 20 Apr 2026 10:31:45 -0600 From: Keith Busch To: alistair23@gmail.com Cc: hare@suse.de, axboe@kernel.dk, hch@lst.de, sagi@grimberg.me, kch@nvidia.com, linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org, Alistair Francis , Chris Leech Subject: Re: [PATCH v3] nvme-auth: Include SC_C in RVAL controller hash Message-ID: References: <20260417005048.2898121-1-alistair.francis@wdc.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: <20260417005048.2898121-1-alistair.francis@wdc.com> On Fri, Apr 17, 2026 at 10:50:48AM +1000, alistair23@gmail.com wrote: > From: Alistair Francis > > Section 8.3.4.5.5 of the NVMe Base Specification 2.1 describes what is > included in the Response Value (RVAL) hash and SC_C should be included. > Currently we are hardcoding 0 instead of using the correct SC_C value. > > Update the host and target code to use the SC_C when calculating the > RVAL instead of using 0. Thanks, applied to nvme-7.1.