From: Blue Swirl <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [6545] Fix SIGSEGV crash in slirp networking code
Date: Fri, 06 Feb 2009 21:37:40 +0000 [thread overview]
Message-ID: <E1LVYOK-000069-Vw@cvs.savannah.gnu.org> (raw)
Revision: 6545
http://svn.sv.gnu.org/viewvc/?view=rev&root=qemu&revision=6545
Author: blueswir1
Date: 2009-02-06 21:37:40 +0000 (Fri, 06 Feb 2009)
Log Message:
-----------
Fix SIGSEGV crash in slirp networking code
Fix SIGSEGV crash in networking code (bug was introduced in r6288).
Thanks to Gleb Natapov for finding this fix.
Signed-off-by: Stefan Weil <weil@mail.berlios.de>
Modified Paths:
--------------
trunk/slirp/ip_input.c
Modified: trunk/slirp/ip_input.c
===================================================================
--- trunk/slirp/ip_input.c 2009-02-06 21:30:02 UTC (rev 6544)
+++ trunk/slirp/ip_input.c 2009-02-06 21:37:40 UTC (rev 6545)
@@ -392,8 +392,7 @@
* into the new buffer.
*/
if (m->m_flags & M_EXT) {
- int delta;
- delta = (char *)ip - m->m_dat;
+ int delta = (char *)q - m->m_dat;
q = (struct ipasfrag *)(m->m_ext + delta);
}
reply other threads:[~2009-02-06 21:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=E1LVYOK-000069-Vw@cvs.savannah.gnu.org \
--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).