From: Jason Wang <jasowang@redhat.com>
To: Mauro Matteo Cascella <mcascell@redhat.com>, qemu-devel@nongnu.org
Cc: gaoning.pgn@antgroup.com, 330cjfdn@gmail.com,
dmitry.fleytman@gmail.com, lersek@redhat.com
Subject: Re: [PATCH] net/e1000e_core: make sure RDH never exceeds RDT in e1000e_ring_advance()
Date: Mon, 9 Nov 2020 10:38:01 +0800 [thread overview]
Message-ID: <b34f724a-b4fc-6dbd-b660-2dfc2b8e943f@redhat.com> (raw)
In-Reply-To: <20201105105616.327593-1-mcascell@redhat.com>
On 2020/11/5 下午6:56, Mauro Matteo Cascella wrote:
> The e1000e_write_packet_to_guest() function iterates over a set of
> receive descriptors by advancing rx descriptor head register (RDH) from
> its initial value to rx descriptor tail register (RDT). The check in
> e1000e_ring_empty() is responsible for detecting whether RDH has reached
> RDT, terminating the loop if that's the case. Additional checks have
> been added in the past to deal with bogus values submitted by the guest
> to prevent possible infinite loop. This is done by "wrapping around" RDH
> at some point and detecting whether it assumes the original value during
> the loop.
>
> However, when e1000e is configured to use the packet split feature, RDH is
> incremented by two instead of one, as the packet split descriptors are
> 32 bytes while regular descriptors are 16 bytes. A malicious or buggy
> guest may set RDT to an odd value and transmit only null RX descriptors.
> This corner case would prevent RDH from ever matching RDT, leading to an
> infinite loop. This patch adds a check in e1000e_ring_advance() to make
> sure RDH does never exceed RDT.
>
> This issue was independently reported by Gaoning Pan (Zhejiang University)
> and Cheolwoo Myung.
>
> Signed-off-by: Mauro Matteo Cascella <mcascell@redhat.com>
> Reported-by: Gaoning Pan <gaoning.pgn@antgroup.com>
> Reported-by: Cheolwoo Myung <330cjfdn@gmail.com>
> ---
> References:
> https://git.qemu.org/?p=qemu.git;a=commit;h=dd793a74882477ca38d49e191110c17dfe
> https://git.qemu.org/?p=qemu.git;a=commit;h=4154c7e03fa55b4cf52509a83d50d6c09d743b7
> http://www.intel.com/content/dam/doc/datasheet/82574l-gbe-controller-datasheet.pdf
>
> hw/net/e1000e_core.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/hw/net/e1000e_core.c b/hw/net/e1000e_core.c
> index bcd186cac5..4c4d14b6ed 100644
> --- a/hw/net/e1000e_core.c
> +++ b/hw/net/e1000e_core.c
> @@ -831,6 +831,10 @@ e1000e_ring_advance(E1000ECore *core, const E1000E_RingInfo *r, uint32_t count)
> {
> core->mac[r->dh] += count;
>
> + if (core->mac[r->dh] > core->mac[r->dt]) {
> + core->mac[r->dh] = core->mac[r->dt];
> + }
> +
> if (core->mac[r->dh] * E1000_RING_DESC_LEN >= core->mac[r->dlen]) {
> core->mac[r->dh] = 0;
> }
A question here.
When count > 1, is this correct to reset dh here?
Thanks
next prev parent reply other threads:[~2020-11-09 2:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-05 10:56 [PATCH] net/e1000e_core: make sure RDH never exceeds RDT in e1000e_ring_advance() Mauro Matteo Cascella
2020-11-05 11:21 ` Mauro Matteo Cascella
2020-11-09 2:38 ` Jason Wang [this message]
2020-11-10 9:06 ` Mauro Matteo Cascella
2020-11-11 8:54 ` Jason Wang
2020-11-11 12:48 ` Jason Wang
2020-11-12 10:20 ` Mauro Matteo Cascella
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=b34f724a-b4fc-6dbd-b660-2dfc2b8e943f@redhat.com \
--to=jasowang@redhat.com \
--cc=330cjfdn@gmail.com \
--cc=dmitry.fleytman@gmail.com \
--cc=gaoning.pgn@antgroup.com \
--cc=lersek@redhat.com \
--cc=mcascell@redhat.com \
--cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).