From: Oleksii Shevchuk <alxchk@gmail.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Oleksii Shevchuk <alxchk@gmail.com>,
Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] qemu git (f03d07d46) / e100 / sending large packets causes SIGABRT
Date: Mon, 29 Jul 2013 15:03:28 +0300 [thread overview]
Message-ID: <87fvuxzi7j.fsf@gmail.com> (raw)
In-Reply-To: <CAJSP0QVSJ7=qCDCCpHvX9+=FNBx7=FR=jtza7SOHt3KqeCWbPA@mail.gmail.com> (Stefan Hajnoczi's message of "Mon, 29 Jul 2013 13:40:42 +0200")
Stefan Hajnoczi <stefanha@gmail.com> writes:
> Oleksii, are you able to test Paolo's patch?
Issue goes away with the patch applied to the current git. At least, it doesn't
reproduce with large packets.
prev parent reply other threads:[~2013-07-29 12:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-24 10:17 [Qemu-devel] qemu git (f03d07d46) / e100 / sending large packets causes SIGABRT Oleksii Shevchuk
2013-07-29 8:50 ` Stefan Hajnoczi
2013-07-29 10:53 ` Paolo Bonzini
2013-07-29 11:40 ` Stefan Hajnoczi
2013-07-29 12:03 ` Oleksii Shevchuk [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=87fvuxzi7j.fsf@gmail.com \
--to=alxchk@gmail.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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 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).