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 8CACC374731 for ; Sat, 4 Jul 2026 02:06:07 +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=1783130768; cv=none; b=Js+AOiU86Z6VD3NMo0y9BoMBT2pgMVQPu/S0rLbHbw7GWXlqnlbkjAOPdOgsb1Zno4tkzGZAiOd42TNmCMwcl0B/o53ecD7L3SX8JsiAfMY4NOyHTut314lITyIzNvwkeZ1D/ttpgay8vBT7vO6rZy6rP9gnOmV47WGi14Tv1kM= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1783130768; c=relaxed/simple; bh=FBFq9dAeCVni7zkMjICeLLc0tapwVo8wQIxEYfmQo5k=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version; b=pt+gV/Mnks803pjSatVKwUVEUWRcsbmcQ+wgMSNgVritic7VURO6N7+vPkoWMy3kkJcyPf4ZDdqmQRE3GDIC4eEBYCpRQW/9zjW89xUlREi6qA+AwYAbQRPNMvx7EaF8GMBCFskR3MV4fE03jWFNVaA5iPaO5GmcG2jp2/AC0qU= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=S79PiGOU; 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="S79PiGOU" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 589371F000E9; Sat, 4 Jul 2026 02:06:06 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1783130767; bh=DyoPHs4l3/dZFD3QTBOPCkOSjHYt8zbBJsp7JlbbYZY=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=S79PiGOUs5t7XFr4fSqE6G5xF3rpMDCVtYQPZwrgU0IKrK0gdidrETMacBte6j512 3m9PDjwD0MSc8a7LkZ40/uV9z/lwhNwlUjDVMrDPFdIclHMvmq01pGTfmqYvm1KnWG +E+FHqgww09faeX2x+Dfg9783iUZffxrCFp2Flv08cMr8RjGTvljHAHdgrinAou9O0 3yFxIde/5A0fIUdhDeDh82thH9HXL/XoJwBYkUIVyTNvwT8yvAatp3sZgruWKF++s7 0XDO5Z22JmIADusNr6T3gKBATWpLtVDhYkT8UzuyDpsVBSUcoZVZzxXH9OMVdlSlY0 bzcm9hQXBPPHw== From: Sasha Levin To: stable@vger.kernel.org Cc: Sasha Levin , "Michael S . Tsirkin" , Jason Wang , Hyokyung Kim Subject: Re: [PATCH 6.6.y] virtio_net: clamp rss_indir_table_size to VIRTIO_NET_RSS_MAX_TABLE_LEN Date: Fri, 3 Jul 2026 22:05:24 -0400 Message-ID: <2026070315-stable-reply-0030@kernel.org> X-Mailer: git-send-email 2.53.0 In-Reply-To: <20260703105059.3821189-1-pulpannie@gmail.com> References: <20260703105059.3821189-1-pulpannie@gmail.com> Precedence: bulk X-Mailing-List: stable@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit On Thu, Jul 03, 2026 at 07:50:59PM +0900, Hyokyung Kim wrote: > This was fixed upstream by commit 86a48a00efdf ("virtio_net: Support > dynamic rss indirection table size"), which reworks the driver to > allocate the indirection table dynamically. However that change is too > large to backport to stable. Instead, clamp the device-advertised length Thanks for working on this, and for the KASAN/UBSAN testing. However, rather than a stable-only clamp that deviates from what upstream did, I'd prefer a proper backport of 86a48a00efdf ("virtio_net: Support dynamic rss indirection table size") with the conflicts resolved for 6.6.y and 6.1.y. Staying aligned with upstream keeps future backports to these trees from getting harder, and avoids carrying behavior that was never reviewed upstream. -- Thanks, Sasha