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 0/3] net: tulip: add checks to avoid OOB access
Date: Thu, 19 Mar 2020 15:22:08 +0530 [thread overview]
Message-ID: <20200319095211.741445-1-ppandit@redhat.com> (raw)
From: Prasad J Pandit <pjp@fedoraproject.org>
Hello,
* This series adds checks to avoid potential OOB access and infinite loop
issues while processing rx/tx data.
* Tulip tx descriptors are capped at 128 to avoid infinite loop in
tulip_xmit_list_update(), wrt Tulip kernel driver
-> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/net/ethernet/dec/tulip/tulip.h#n319
* Update v3: add .can_receive routine
-> https://lists.gnu.org/archive/html/qemu-devel/2020-02/msg06275.html
* Update v4: flush queued packets once they are received
-> https://lists.gnu.org/archive/html/qemu-devel/2020-03/msg05868.html
Thank you.
--
Prasad J Pandit (3):
net: tulip: check frame size and r/w data length
net: tulip: add .can_recieve routine
net: tulip: flush queued packets post receive
hw/net/tulip.c | 51 +++++++++++++++++++++++++++++++++++++++++---------
1 file changed, 42 insertions(+), 9 deletions(-)
--
2.25.1
next 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 P J P [this message]
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 ` [PATCH v4 3/3] net: tulip: flush queued packets post receive P J P
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-1-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).