From: Vladimir Petrzhikovskii <vladimir@dfb.sh>
To: netdev-bot+sashiko@kernel.org
Cc: netdev@vger.kernel.org, mst@redhat.com, jasowangio@gmail.com,
eperezma@redhat.com, xuanzhuo@linux.alibaba.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@kernel.org,
kuba@kernel.org, pabeni@redhat.com, vishs@meta.com,
virtualization@lists.linux.dev, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, nikolai@kalinidze.me
Subject: Re: [PATCH net] virtio_net: check RX buffer length before DMA sync
Date: Tue, 10 Nov 2026 16:36:57 +0100 [thread overview]
Message-ID: <20261110153657.599022-1-vladimir@dfb.sh> (raw)
In-Reply-To: <179425939711.994134.2719389056327615125@kernel.org>
On Mon, 09 Nov 2026 21:23:17 +0000, netdev-bot+sashiko@kernel.org wrote:
> Should the Fixes: tag point at 295525e29a5b and/or fb22437c1ba3? It would
> also help to say in the changelog that those trees need a separate fix,
> for example limiting the sync in virtnet_rq_unmap() to the posted length.
Yes, this is right. Since 295525e29a5b virtnet_rq_unmap() syncs with the
used length before any length check, and the mapping covers the whole
frag, so those kernels have the same problem.
v2 will carry Fixes: 295525e29a5b and say in the changelog that kernels
before v7.1 need a separate backport. No code change. We will prepare
that backport for stable separately.
pw-bot: cr
prev parent reply other threads:[~2026-11-10 15:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-08 21:09 [PATCH net] virtio_net: check RX buffer length before DMA sync Vladimir Petrzhikovskii
2026-11-09 21:23 ` netdev-bot+sashiko
2026-11-10 15:36 ` Vladimir Petrzhikovskii [this message]
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=20261110153657.599022-1-vladimir@dfb.sh \
--to=vladimir@dfb.sh \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=eperezma@redhat.com \
--cc=jasowangio@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev-bot+sashiko@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nikolai@kalinidze.me \
--cc=pabeni@redhat.com \
--cc=stable@vger.kernel.org \
--cc=virtualization@lists.linux.dev \
--cc=vishs@meta.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox