From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>,
"Michael S . Tsirkin" <mst@redhat.com>,
Jason Wang <jasowang@redhat.com>,
Philo Lu <lulie@linux.alibaba.com>,
Xuan Zhuo <xuanzhuo@linux.alibaba.com>,
Joe Damato <jdamato@fastly.com>, Paolo Abeni <pabeni@redhat.com>,
Hyokyung Kim <pulpannie@gmail.com>
Subject: Re: [PATCH 6.1.y] virtio_net: Support dynamic rss indirection table size
Date: Fri, 10 Jul 2026 17:03:02 -0400 [thread overview]
Message-ID: <20260710163023.agent5-0006@kernel.org> (raw)
In-Reply-To: <20260710112521.234909-1-pulpannie@gmail.com>
On Fri, Jul 10, 2026 at 11:25:21AM +0000, Hyokyung Kim wrote:
> However, the indirection_table was statically sized as
> VIRTIO_NET_RSS_MAX_TABLE_LEN=128, potentially causing issues when
> vi->rss_indir_table_size exceeds this limit.
>
> This patch implements dynamic allocation for the indirection table,
> allocated alongside vi->rss after vi->rss_indir_table_size is initialized,
> and freed in virtnet_remove().
Queued for 6.1, thanks.
--
Thanks,
Sasha
next prev parent reply other threads:[~2026-07-10 21:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-30 0:51 [LTS Backport Request] Fix RSS indirection table OOB write (6.1.y, 6.6.y) Annie Kim
2026-06-30 22:23 ` Sasha Levin
2026-07-03 10:50 ` [PATCH 6.6.y] virtio_net: clamp rss_indir_table_size to VIRTIO_NET_RSS_MAX_TABLE_LEN Hyokyung Kim
2026-07-04 2:05 ` Sasha Levin
2026-07-06 5:48 ` Annie Kim
2026-07-03 10:52 ` [PATCH 6.1.y] " Hyokyung Kim
2026-08-20 13:49 ` Greg KH
2026-08-21 4:33 ` Sasha Levin
2026-07-10 11:19 ` [PATCH 6.6.y] virtio_net: Support dynamic rss indirection table size Hyokyung Kim
2026-07-10 21:03 ` Sasha Levin
2026-07-10 11:25 ` [PATCH 6.1.y] " Hyokyung Kim
2026-07-10 21:03 ` Sasha Levin [this message]
2026-07-10 12:49 ` [PATCH 6.6.y] " Hyokyung Kim
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260710163023.agent5-0006@kernel.org \
--to=sashal@kernel.org \
--cc=jasowang@redhat.com \
--cc=jdamato@fastly.com \
--cc=lulie@linux.alibaba.com \
--cc=mst@redhat.com \
--cc=pabeni@redhat.com \
--cc=pulpannie@gmail.com \
--cc=stable@vger.kernel.org \
--cc=xuanzhuo@linux.alibaba.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.