From: P J P <ppandit@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: Alexander Bulekov <alxndr@bu.edu>,
Cheolwoo Myung <cwmyung@snu.ac.kr>,
Ruhr-University Bochum <bugs-syssec@rub.de>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [PATCH] net: e1000: check transmit descriptor field values
Date: Thu, 18 Feb 2021 13:17:47 +0530 (IST) [thread overview]
Message-ID: <4696sr1n-7p2o-6725-s02n-4o158pq38r35@erqung.pbz> (raw)
In-Reply-To: <86ea17a0-fd8b-53d5-f975-c55b19e9005d@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 830 bytes --]
Hello Jason,
+-- On Thu, 18 Feb 2021, Jason Wang wrote --+
| On 2021/2/10 下午10:52, P J P wrote:
| > From: Prasad J Pandit <pjp@fedoraproject.org>
| >
| > While processing transmit (tx) descriptors in process_tx_desc()
| > various descriptor fields are not checked properly. This may lead
| > to infinite loop like issue. Add checks to avoid them.
| >
| > Reported-by: Alexander Bulekov <alxndr@bu.edu>
| > Reported-by: Cheolwoo Myung <cwmyung@snu.ac.kr>
| > Reported-by: Ruhr-University Bochum <bugs-syssec@rub.de>
| > Signed-off-by: Prasad J Pandit <pjp@fedoraproject.org>
| > ---
| > hw/net/e1000.c | 6 ++++++
| > 1 file changed, 6 insertions(+)
|
| I guess you post the wrong patch :) ?
Wrong patch...?
Thank you.
--
Prasad J Pandit / Red Hat Product Security Team
8685 545E B54C 486B C6EB 271E E285 8B5A F050 DE8D
next prev parent reply other threads:[~2021-02-18 7:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-10 14:52 [PATCH] net: e1000: check transmit descriptor field values P J P
2021-02-18 5:53 ` Jason Wang
2021-02-18 7:47 ` P J P [this message]
2021-02-19 2:53 ` Jason Wang
2021-02-19 3:05 ` Alexander Bulekov
2021-02-19 9:01 ` P J P
2021-02-19 10:27 ` Peter Maydell
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=4696sr1n-7p2o-6725-s02n-4o158pq38r35@erqung.pbz \
--to=ppandit@redhat.com \
--cc=alxndr@bu.edu \
--cc=bugs-syssec@rub.de \
--cc=cwmyung@snu.ac.kr \
--cc=jasowang@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.