From: Sasha Levin <sashal@kernel.org>
To: Hyokyung Kim <pulpannie@gmail.com>
Cc: Sasha Levin <sashal@kernel.org>,
stable@vger.kernel.org, "Michael S . Tsirkin" <mst@redhat.com>,
Jason Wang <jasowang@redhat.com>,
Greg KH <gregkh@linuxfoundation.org>
Subject: Re: [PATCH 6.1.y] virtio_net: clamp rss_indir_table_size to VIRTIO_NET_RSS_MAX_TABLE_LEN
Date: Fri, 21 Aug 2026 00:33:34 -0400 [thread overview]
Message-ID: <20260821-stable-item009-virtio-rss-clamp@kernel.org> (raw)
In-Reply-To: <2026082033-driven-tumbling-f69d@gregkh>
> Why is it "too large"? Again, we want to keep as close as possible to
> upstream as diverging will cause bugs and maintenance problems over
> time.
The question is moot now - this one can just be dropped from the queue.
Hyokyung followed up with an upstream-shaped backport of 86a48a00efdf
("virtio_net: Support dynamic rss indirection table size"), and that already
shipped in 6.1.178 and 6.6.145.
--
Thanks,
Sasha
next prev parent reply other threads:[~2026-08-21 4:33 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 [this message]
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
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=20260821-stable-item009-virtio-rss-clamp@kernel.org \
--to=sashal@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=pulpannie@gmail.com \
--cc=stable@vger.kernel.org \
/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.