From: P J P <ppandit@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: Prasad J Pandit <pjp@fedoraproject.org>,
Stefan Hajnoczi <stefanha@gmail.com>,
Qemu Developers <qemu-devel@nongnu.org>,
Li Qiang <pangpei.lq@antfin.com>,
Sven Schnelle <svens@stackframe.org>,
Ziming Zhang <ezrakiez@gmail.com>
Subject: [PATCH v4 3/3] net: tulip: flush queued packets post receive
Date: Thu, 19 Mar 2020 15:22:11 +0530 [thread overview]
Message-ID: <20200319095211.741445-4-ppandit@redhat.com> (raw)
In-Reply-To: <20200319095211.741445-1-ppandit@redhat.com>
From: Prasad J Pandit <pjp@fedoraproject.org>
Call qemu_flush_queued_packets to flush queued packets once they
are read in tulip_receive().
Suggested-by: Jason Wang <jasowang@redhat.com>
Signed-off-by: Prasad J Pandit <pjp@fedoraproject.org>
---
hw/net/tulip.c | 2 ++
1 file changed, 2 insertions(+)
Update v4: call qemu_flush_queued_packets()
-> https://lists.gnu.org/archive/html/qemu-devel/2020-03/msg05868.html
diff --git a/hw/net/tulip.c b/hw/net/tulip.c
index 757f12c710..8d8c9519e7 100644
--- a/hw/net/tulip.c
+++ b/hw/net/tulip.c
@@ -287,6 +287,8 @@ static ssize_t tulip_receive(TULIPState *s, const uint8_t *buf, size_t size)
tulip_desc_write(s, s->current_rx_desc, &desc);
tulip_next_rx_descriptor(s, &desc);
} while (s->rx_frame_len);
+
+ qemu_flush_queued_packets(qemu_get_queue(s->nic));
return size;
}
--
2.25.1
prev parent reply other threads:[~2020-03-19 9:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-19 9:52 [PATCH v4 0/3] net: tulip: add checks to avoid OOB access P J P
2020-03-19 9:52 ` [PATCH v4 1/3] net: tulip: check frame size and r/w data length P J P
2020-03-19 9:52 ` [PATCH v4 2/3] net: tulip: add .can_recieve routine P J P
2020-03-19 10:24 ` Philippe Mathieu-Daudé
2020-03-19 17:47 ` P J P
2020-03-19 9:52 ` P J P [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=20200319095211.741445-4-ppandit@redhat.com \
--to=ppandit@redhat.com \
--cc=ezrakiez@gmail.com \
--cc=jasowang@redhat.com \
--cc=pangpei.lq@antfin.com \
--cc=pjp@fedoraproject.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=svens@stackframe.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).