From: Jan Kiszka <jan.kiszka@web.de>
Cc: Stefan Weil <sw@weilnetz.de>,
Zhi Yong Wu <wuzhy@linux.vnet.ibm.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Fabien Chouteau <chouteau@adacore.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 0/4] slirp: Fix for requeuing crash, cleanups
Date: Tue, 06 Mar 2012 08:41:38 +0100 [thread overview]
Message-ID: <4F55BFB2.5080803@web.de> (raw)
In-Reply-To: <4F548233.9010908@siemens.com>
[-- Attachment #1: Type: text/plain, Size: 535 bytes --]
On 2012-03-05 10:06, Jan Kiszka wrote:
> Grmbl. Was very hard to reproduce here (triggered once every few hours
> with lots of interaction beforehand), but now I think I got the point
> (recursion of if_start due to if_encap). Will rework the code to address
> this.
>
> Thanks for testing so far, will likely need your services again soon.
I'm careful now with claiming it's fixed, but this version
git://git.kiszka.org/qemu.git queues/slirp
passes all tests that broke in the past. Please have another try.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2012-03-06 7:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-02 18:57 [Qemu-devel] [PATCH v2 0/4] slirp: Fix for requeuing crash, cleanups Jan Kiszka
2012-03-02 18:57 ` [Qemu-devel] [PATCH v2 1/4] slirp: Keep next_m always valid Jan Kiszka
2012-03-02 18:57 ` [Qemu-devel] [PATCH v2 2/4] slirp: Fix queue walking in if_start Jan Kiszka
2012-03-02 18:57 ` [Qemu-devel] [PATCH v2 3/4] slirp: Remove unneeded if_queued Jan Kiszka
2012-03-02 18:57 ` [Qemu-devel] [PATCH v2 4/4] slirp: Cleanup resources on instance removal Jan Kiszka
2012-03-02 21:05 ` [Qemu-devel] [PATCH v2 0/4] slirp: Fix for requeuing crash, cleanups Stefan Weil
2012-03-05 9:06 ` Jan Kiszka
2012-03-06 7:41 ` Jan Kiszka [this message]
2012-03-07 21:42 ` 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=4F55BFB2.5080803@web.de \
--to=jan.kiszka@web.de \
--cc=chouteau@adacore.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sw@weilnetz.de \
--cc=wuzhy@linux.vnet.ibm.com \
/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.