qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: P J P <ppandit@redhat.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
	Sven Schnelle <svens@stackframe.org>,
	Qemu Developers <qemu-devel@nongnu.org>,
	Ziming Zhang <ezrakiez@gmail.com>,
	Li Qiang <pangpei.lq@antfin.com>
Subject: Re: [PATCH v3 2/2] net: tulip: add .can_recieve routine
Date: Wed, 18 Mar 2020 10:07:34 +0800	[thread overview]
Message-ID: <976adb02-5653-2f57-555d-c41b8d392fc1@redhat.com> (raw)
In-Reply-To: <nycvar.YSQ.7.76.2003171543480.5086@xnncv>


On 2020/3/17 下午6:49, P J P wrote:
> +-- On Tue, 17 Mar 2020, Jason Wang wrote --+
> | > +-- On Fri, 6 Mar 2020, Stefan Hajnoczi wrote --+
> | > | > +static int
> | > | > +tulip_can_receive(NetClientState *nc)
> | > | > +{
> | > | > +    TULIPState *s = qemu_get_nic_opaque(nc);
> | > | > +
> | > | > +    if (s->rx_frame_len || tulip_rx_stopped(s)) {
> | > | > +        return false;
> | > | > +    }
> |
> | Btw, what's the point of checking rx_frame_len here?
>
> tulip_can_recive() is called from tulip_receive(). IIUC non zero(0)
> 'rx_frame_len' hints that s->rs_frame[] buffer still has unread data bytes and
> it can not receive new bytes. The check was earlier in tulip_receive().


Right, so need to make sure qemu_flush_ququed_packets() was called when 
rx_frame_len is zero.

Thanks



>
> Thank you.
> --
> Prasad J Pandit / Red Hat Product Security Team
> 8685 545E B54C 486B C6EB 271E E285 8B5A F050 DE8D



  reply	other threads:[~2020-03-18  2:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-03 10:47 [PATCH v3 0/2] net: tulip: add checks to avoid OOB access P J P
2020-03-03 10:47 ` [PATCH v3 1/2] net: tulip: check frame size and r/w data length P J P
2020-03-03 10:47 ` [PATCH v3 2/2] net: tulip: add .can_recieve routine P J P
2020-03-06 13:08   ` Stefan Hajnoczi
2020-03-16 18:01     ` P J P
2020-03-17  5:50       ` Jason Wang
2020-03-17 10:49         ` P J P
2020-03-18  2:07           ` Jason Wang [this message]
2020-03-19  9:58             ` P J P
2020-03-03 10:54 ` [PATCH v3 0/2] net: tulip: add checks to avoid OOB access no-reply
2020-03-05 12:16   ` P J P
2020-03-03 10:54 ` no-reply
2020-03-03 10:54 ` no-reply
2020-03-03 10:56 ` no-reply

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=976adb02-5653-2f57-555d-c41b8d392fc1@redhat.com \
    --to=jasowang@redhat.com \
    --cc=ezrakiez@gmail.com \
    --cc=pangpei.lq@antfin.com \
    --cc=ppandit@redhat.com \
    --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).