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 CB6E72C029F for ; Mon, 17 Nov 2025 16:06:20 +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=1763395580; cv=none; b=gdbo1be9zgD8tIG8KnEh2LNb5tjZkZo9aKhtkBD2zGOiXRuP/C+urqIMxQ+PdU7/3NQQKVwfzhVBjKYvDMebBUsg8hH4gZxAYRPV5vORlo9zpZw1TRmdSdfN0ip+xeTYdw5y+XBnv8TR5sUSBYMRGABwB9yoUmbGWFhb4Qxr5Ro= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1763395580; c=relaxed/simple; bh=b5BOGptpiRe/9KC7/lrPlrgkSCv7d74hQqIOtfkcccU=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=Y0pnxA9IHdS7MqiRzwoPMNklVgi6VzyXxSVwlKuJFM5QKUSeDbx5UCDIkStd7jbEHiD7tjPInqRS1ygWHh9G4eofxQ1mGM3uqNNsyAdV/PiIPNsuNWWCy2ZpayxEmvUM4wKIx0is88TxKh93X880OcmT7nBEz8Fb4iT/4vHoYfA= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=JBocGp4o; 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="JBocGp4o" Received: by smtp.kernel.org (Postfix) with ESMTPSA id DC6CAC113D0; Mon, 17 Nov 2025 16:06:19 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1763395580; bh=b5BOGptpiRe/9KC7/lrPlrgkSCv7d74hQqIOtfkcccU=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=JBocGp4o+5KNpR49mo4qUuo4alUCh8x4ZCfazoic0HYPWQFjQJN4nQKTY19EGC2vv coHj3tBNNXe3d/3Ou9tMvnWuGuO7i/3zNjHM9pJy7XnhkRi71O+44wWRA2TwE8sQHY q2Z6lDQ3A0PYb+6UQMJ+0SzcOL0Be90adVnJz4VucQ0kRuKCiOT+3vVJBm8Z7HFpsr 7sTni96I6VwvbsdCO8TLJEYnC7CmB+BnvpbfNtp72oJTRzON2fFCzDLu9PbBeX6SHc Enzht9yU7/1GDfdkSVegcYJJUkZEm/fQF/Zziujt2wgHdA7DRx8CPzLWNVN/wZlxg3 r49ZgUIOUxW8g== Date: Mon, 17 Nov 2025 09:06:18 -0700 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 Subject: Re: [PATCH v3] nvmet-auth: update sc_c in target host hash calculation Message-ID: References: <20251106231711.3189836-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: <20251106231711.3189836-1-alistair.francis@wdc.com> On Fri, Nov 07, 2025 at 09:17:11AM +1000, alistair23@gmail.com wrote: > From: Alistair Francis > > Commit 7e091add9c43 "nvme-auth: update sc_c in host response" added > the sc_c variable to the dhchap queue context structure which is > appropriately set during negotiate and then used in the host response. > > This breaks secure concat connections with a Linux target as the target > code wasn't updated at the same time. This patch fixes this by adding a > new sc_c variable to the host hash calculations. Thanks, applied to nvme-6.18.