From: "Philippe Mathieu-Daudé" <1837094@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1837094] Re: UndefinedBehaviorSanitizer crash around slirp::ip_reass()
Date: Thu, 18 Jul 2019 17:58:55 -0000 [thread overview]
Message-ID: <156347273572.17826.9232171391242011623.launchpad@gac.canonical.com> (raw)
In-Reply-To: 156347205992.30489.16276823737610194084.malonedeb@soybean.canonical.com
** Description changed:
tag: v4.1.0-rc1
./configure --enable-sanitizers --extra-cflags=-O1
- ==26130==ERROR: UndefinedBehaviorSanitizer: SEGV on unknown address 0x000000000008 (pc 0x00000046d588 bp 0x7fff6ee9f940 sp 0x7fff6ee9f8e8 T26130)
+ ==26130==ERROR: UndefinedBehaviorSanitizer: SEGV on unknown address 0x000000000008 (pc 0x0000561ad346d588 bp 0x7fff6ee9f940 sp 0x7fff6ee9f8e8 T26130)
==26130==The signal is caused by a WRITE memory access.
==26130==Hint: address points to the zero page.
- #0 0x0000561ad346d587 in ip_deq() at slirp/src/ip_input.c:411:55
- #1 0x0000561ad346cffb in ip_reass() at slirp/src/ip_input.c:304:9
- #2 0x0000561ad346cb6f in ip_input() at slirp/src/ip_input.c:184:18
+ #0 0x0000561ad346d587 in ip_deq() at slirp/src/ip_input.c:411:55
+ #1 0x0000561ad346cffb in ip_reass() at slirp/src/ip_input.c:304:9
+ #2 0x0000561ad346cb6f in ip_input() at slirp/src/ip_input.c:184:18
I only had access to the last packet which isn't the culprit, I'm now
seeing how to log the network traffic of the guest to provide more
useful information.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1837094
Title:
UndefinedBehaviorSanitizer crash around slirp::ip_reass()
Status in QEMU:
New
Bug description:
tag: v4.1.0-rc1
./configure --enable-sanitizers --extra-cflags=-O1
==26130==ERROR: UndefinedBehaviorSanitizer: SEGV on unknown address 0x000000000008 (pc 0x0000561ad346d588 bp 0x7fff6ee9f940 sp 0x7fff6ee9f8e8 T26130)
==26130==The signal is caused by a WRITE memory access.
==26130==Hint: address points to the zero page.
#0 0x0000561ad346d587 in ip_deq() at slirp/src/ip_input.c:411:55
#1 0x0000561ad346cffb in ip_reass() at slirp/src/ip_input.c:304:9
#2 0x0000561ad346cb6f in ip_input() at slirp/src/ip_input.c:184:18
I only had access to the last packet which isn't the culprit, I'm now
seeing how to log the network traffic of the guest to provide more
useful information.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1837094/+subscriptions
next prev parent reply other threads:[~2019-07-18 18:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-18 17:47 [Qemu-devel] [Bug 1837094] [NEW] UndefinedBehaviorSanitizer crash around slirp::ip_reass() Philippe Mathieu-Daudé
2019-07-18 17:58 ` Philippe Mathieu-Daudé [this message]
2019-08-29 15:16 ` [Qemu-devel] [Bug 1837094] " Philippe Mathieu-Daudé
2019-08-29 15:39 ` Samuel thibault
2020-05-18 8:13 ` Philippe Mathieu-Daudé
2020-05-18 8:14 ` Philippe Mathieu-Daudé
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=156347273572.17826.9232171391242011623.launchpad@gac.canonical.com \
--to=1837094@bugs.launchpad.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).