qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Blue Swirl" <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] core dump on networking and old pkgsrc patches
Date: Tue, 1 Jul 2008 23:10:50 +0300	[thread overview]
Message-ID: <f43fc5580807011310g22c4e47dwccd9a890b23317e6@mail.gmail.com> (raw)
In-Reply-To: <Pine.NEB.4.64.0807011119030.17719@tx.reedmedia.net>

On 7/1/08, Jeremy C. Reed <reed@reedmedia.net> wrote:
> This is a problem that may already be fixed.

Not yet, even though several people have tried and failed.

>  #0  0x000000000046bfef in tcp_reass (tp=0x7f7ffb238180, ti=0xfb238180,
>  m=0x0)
>     at /usr/pkgsrc/emulators/qemu/work/qemu-0.9.0/slirp/tcp_input.c:207
>  207             if (ti == (struct tcpiphdr *)tp || ti->ti_seq !=
>  tp->rcv_nxt)

SLIRP re-uses some of the 32 bit TCP/IP header fields as storage for
pointers. This works on a 32 bit host and in some lucky cases on a
x86-64.

Please visit
http://lists.gnu.org/archive/html/qemu-devel/2008-01/msg00725.html

      reply	other threads:[~2008-07-01 20:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-01 16:26 [Qemu-devel] core dump on networking and old pkgsrc patches Jeremy C. Reed
2008-07-01 20:10 ` Blue Swirl [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=f43fc5580807011310g22c4e47dwccd9a890b23317e6@mail.gmail.com \
    --to=blauwirbel@gmail.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 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).