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 1666139D6D9
	for <linux-kernel@vger.kernel.org>; Tue, 28 Jul 2026 17:14:48 +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=1785258890; cv=none; b=FBiArdDCU6LLqycr0Pmpj/UwMQvCLk4Gv9j2MwXJvRqU6xX1QKLaYuWKGj/VgJ05z2XaH7gt/FzbHC6DgU2mqgr48krtwBzH/3pRW859kFrLrMWqSIYxUerDd0dfcFqEDZoPFtwstbpqRZ71s05bU0WPw/nsK+ILir8geq4VhF8=
ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org;
	s=arc-20240116; t=1785258890; c=relaxed/simple;
	bh=xEsuTZ/J/7jYlAh219+aGSAIHCzqRxzX//zpdlhopWw=;
	h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version:
	 Content-Type:Content-Disposition:In-Reply-To; b=lA4IuZx8gowz2RhpNwOtiGPIeJsMy2SkkZUkceRb+m1dW8VWoMtb24BdteTWYnxXflhIIeWr4QJBDCnaeXveEVrreqlNIbA/F5HL7PLg9OyxezCo6utNKwrRnvzLT2pfsIU6iEL6nZ4PkQBJdbHb89igpRRPpYmJoTIG2JYSnsY=
ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=Vzna6AE8; 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="Vzna6AE8"
Received: by smtp.kernel.org (Postfix) with ESMTPSA id C41B21F000E9;
	Tue, 28 Jul 2026 17:14:47 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org;
	s=k20260515; t=1785258888;
	bh=xEsuTZ/J/7jYlAh219+aGSAIHCzqRxzX//zpdlhopWw=;
	h=Date:From:To:Cc:Subject:References:In-Reply-To;
	b=Vzna6AE8VELXvjiBgRNtL2+G4GPkxBK0IjUwTpN0nHa7u3/jsEHbSn5p1meDTZWGW
	 IC8yjU/X9AKMRtIcI7D3XHMS2KPHuUjfKILMDdQX/Q8fZlWs2Jk8ko371BaIXre1q6
	 1KKMNE3LIvs0/cEQYi0EhLWVGaeB+gV5IRMc2OetZHJB1W+PMjPjFylhMsvgqzMTT3
	 oSDy7tHsVBBxr1VuJPIskPf/+1Td1BLqhGlwNM2lCgdcceBRrh8m+0ppuLAjg/pkm8
	 TRjWeHoRLblMYawH4z7iM0kxBbAhJ5fgOAQ78giQITqcUBVGPRuVBcc5zuGAykDgck
	 /OgrHHKhlC7+g==
Date: Tue, 28 Jul 2026 11:14:46 -0600
From: Keith Busch <kbusch@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
	Chaitanya Kulkarni <kch@nvidia.com>, linux-nvme@lists.infradead.org,
	linux-kernel@vger.kernel.org, stable <stable@kernel.org>
Subject: Re: [PATCH] nvmet-tcp: Do not WARN on remotely-controlled oversized
 SGL allocations
Message-ID: <amjjhnBMMcHACoKp@kbusch-mbp>
References: <20260727-nvme-tcp-v1-1-61c0e36763eb@linuxfoundation.org>
Precedence: bulk
X-Mailing-List: linux-kernel@vger.kernel.org
List-Id: <linux-kernel.vger.kernel.org>
List-Subscribe: <mailto:linux-kernel+subscribe@vger.kernel.org>
List-Unsubscribe: <mailto:linux-kernel+unsubscribe@vger.kernel.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20260727-nvme-tcp-v1-1-61c0e36763eb@linuxfoundation.org>

On Mon, Jul 27, 2026 at 10:03:31PM +0200, Greg Kroah-Hartman wrote:
> When fuzzing the nvme target code, I tripped a kernel warning in
> nvmet_tcp_map_data() because the length passed into the allocator is
> controlled by the remote initiator.

Thanks, applied to nvme-7.3 with a minor fix for an overly long line.