From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 60518] Heavy network traffic between guest and host triggers kernel oops
Date: Tue, 13 Aug 2013 18:57:03 +0000 [thread overview]
Message-ID: <bug-60518-28872-0PstElloDd@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-60518-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=60518
Bart Van Assche <bvanassche@acm.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |CODE_FIX
--- Comment #5 from Bart Van Assche <bvanassche@acm.org> ---
Same results on my setup - 3.10.5 passes my tests.
--
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2013-08-13 18:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-05 12:47 [Bug 60518] New: Heavy network traffic between guest and host triggers kernel oops bugzilla-daemon
2013-07-05 15:06 ` [Bug 60518] " bugzilla-daemon
2013-07-07 10:19 ` bugzilla-daemon
2013-08-06 8:55 ` bugzilla-daemon
2013-08-07 12:24 ` bugzilla-daemon
2013-08-13 18:57 ` bugzilla-daemon [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=bug-60518-28872-0PstElloDd@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=kvm@vger.kernel.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).