From: P J P <ppandit@redhat.com>
To: qemu-devel@nongnu.org
Cc: Qinghao Tang <luodalongde@gmail.com>,
Stefan Weil <sw@weilnetz.de>, Jason Wang <jasowang@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] eepro100: prevent an infinite loop over same command block
Date: Sat, 17 Oct 2015 16:55:22 +0530 (IST) [thread overview]
Message-ID: <alpine.LFD.2.20.1510171630500.10659@wniryva> (raw)
In-Reply-To: <56216E1A.30609@weilnetz.de>
Hello,
+-- On Fri, 16 Oct 2015, Stefan Weil wrote --+
| is this just a theoretical assumption or did you see problems
| with some guest operating system?
|
| To trigger a potential infinite loop, you'll need buggy device
| drivers in the guest.
Right; The issue isn't theoretical, it was seen and reported by Mr Qinghao,
CC'd here.
| Maybe real hardware will run an endless loop?
| Or the "endless" loop is terminated because the driver
| changes the link while the loop is running?
IIUC, command execution loop is terminated when 'I', 'EL' or 'S' bits are
set in the current command block, otherwise loop continues to read the next
command block(CB) in the list.
--
- P J P
47AF CE69 3A90 54AA 9045 1053 DD13 3D32 FE5B 041F
next prev parent reply other threads:[~2015-10-17 11:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-16 11:12 [Qemu-devel] [PATCH] eepro100: prevent an infinite loop over same command block P J P
2015-10-16 12:41 ` Paolo Bonzini
2015-10-16 17:19 ` P J P
2015-10-16 21:37 ` Stefan Weil
2015-10-17 11:25 ` P J P [this message]
2015-10-17 11:35 ` Peter Maydell
2015-10-20 3:04 ` Jason Wang
2015-10-20 3:10 ` max
2015-10-20 3:02 ` Jason Wang
2015-11-03 18:49 ` P J P
2015-11-04 3:31 ` Jason Wang
2015-11-20 2:43 ` Qinghao Tang
2015-11-20 6:10 ` P J P
2015-11-20 6:29 ` Qinghao Tang
2015-11-20 7:23 ` P J P
2015-11-20 7:47 ` Stefan Weil
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=alpine.LFD.2.20.1510171630500.10659@wniryva \
--to=ppandit@redhat.com \
--cc=jasowang@redhat.com \
--cc=luodalongde@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=sw@weilnetz.de \
/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).