From: Scott Pakin <pakin@lanl.gov>
To: qemu-devel@nongnu.org, kvm-devel@lists.sourceforge.net
Subject: [Qemu-devel] [PATCH] Making SLIRP code more 64-bit clean
Date: Tue, 29 Jan 2008 10:11:22 -0700 [thread overview]
Message-ID: <479F5E3A.6030506@lanl.gov> (raw)
[-- Attachment #1: Type: text/plain, Size: 588 bytes --]
The attached patch corrects a bug in qemu/slirp/tcp_var.h that defines
the seg_next field in struct tcpcb to be 32 bits wide regardless of
32/64-bitness. seg_next is assigned a pointer value in
qemu/slirp/tcp_subr.c, then cast back to a pointer in qemu/slirp/tcp_input.c
and dereferenced. That produces a SIGSEGV on my system.
For more information, see the thread "[ 1881532 ] Network access seg faults
KVM on large-memory machine" on the KVM Bugs page on SourceForge
(http://tinyurl.com/2fxfbx).
Regards,
-- Scott
P.S. Note: This message was sent to both qemu-devel and kvm-devel.
[-- Attachment #2: tcp_seg_next.patch --]
[-- Type: text/x-patch, Size: 403 bytes --]
--- qemu/slirp/tcp_var.h.ORIG 2008-01-28 17:27:09.000000000 -0700
+++ qemu/slirp/tcp_var.h 2008-01-28 17:27:20.000000000 -0700
@@ -40,11 +40,7 @@
#include "tcpip.h"
#include "tcp_timer.h"
-#if SIZEOF_CHAR_P == 4
- typedef struct tcpiphdr *tcpiphdrp_32;
-#else
- typedef u_int32_t tcpiphdrp_32;
-#endif
+typedef struct tcpiphdr *tcpiphdrp_32;
/*
* Tcp control block, one per tcp; fields:
next reply other threads:[~2008-01-29 17:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-29 17:11 Scott Pakin [this message]
2008-01-30 4:27 ` [Qemu-devel] RE: [kvm-devel] [PATCH] Making SLIRP code more 64-bit clean Zhang, Xiantao
2008-01-30 16:42 ` [Qemu-devel] " Scott Pakin
2008-01-30 17:10 ` Blue Swirl
2008-02-01 1:26 ` [kvm-ia64-devel] [Qemu-devel] Re: [kvm-devel] [PATCH] MakingSLIRP " Zhang, Xiantao
2008-01-31 8:24 ` [Qemu-devel] RE: [kvm-devel] [PATCH] Making SLIRP " Zhang, Xiantao
2008-01-31 18:38 ` [Qemu-devel] " Scott Pakin
2008-02-01 1:37 ` Scott Pakin
2008-02-01 2:44 ` [Qemu-devel] RE: [kvm-ia64-devel] [kvm-devel] [PATCH] Making SLIRP code more64-bit clean Zhang, Xiantao
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=479F5E3A.6030506@lanl.gov \
--to=pakin@lanl.gov \
--cc=kvm-devel@lists.sourceforge.net \
--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).