From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 60518] New: Heavy network traffic between guest and host triggers kernel oops
Date: Fri, 05 Jul 2013 12:47:37 +0000 [thread overview]
Message-ID: <bug-60518-28872@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=60518
Bug ID: 60518
Summary: Heavy network traffic between guest and host triggers
kernel oops
Product: Virtualization
Version: unspecified
Kernel Version: v3.9.8 and v3.9.9
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: kvm
Assignee: virtualization_kvm@kernel-bugs.osdl.org
Reporter: bvanassche@acm.org
Regression: No
When sending network packets at a high rate between KVM guests I either run
into bug 60505 or into the call trace below:
BUG: unable to handle kernel NULL pointer dereference at 000000000000001c
IP: [<ffffffff810f73a9>] put_compound_page+0x89/0x170
PGD 0
Oops: 0000 [#1] SMP
Modules linked in: dm_queue_length dm_multipath rdma_ucm rdma_cm iw_cm ib_addr
ib_srp scsi_transport_srp scsi_tgt ib_ipoib ib_cm ib_uverbs ib_umad mlx4_en
mlx4_ib ib_sa ib_mad ib_core mlx4_core libcrc32c crc32c_intel nls_utf8
iscsi_tcp libisc rt_iscsi vhost_net tun fuse ip6table_filter ip6_tables
iptable_filter ip_tables ebtable_nat ebtables x_tables af_packet bridge stp llc
dm_mod hid_generic usbhid hid snd_hda_codec_hdmi snd_hda_codec_realtek
snd_hda_intel snd_hda_codec acpi_cpuf vm_intel snd_pcm cdrom pcspkr kvm snd_seq
sg snd_timer snd_seq_device snd r8169 ehci_pci ehci_hcd i2c_i801 soundcore wmi
snd_page_alloc mii microcode autofs4 ext4 jbd2 mbcache crc16 raid456
async_raid6_recov async_pq raid6_pq async_xor xor asy id0 raid1 sd_mod
crc_t10dif ahci xhci_hcd libahci i915 drm_kms_helper drm intel_agp i2c_algo_bit
intel_gtt agpgart usbcore i2c_core video usb_common button processor
thermal_sys hwmon scsi_dh_alua scsi_dh pata_acpi libata scsi_mod [last unload
CPU 3
Pid: 30508, comm: vhost-30506 Tainted: G O 3.9.8+ #1 Gigabyte
Technology Co., Ltd. Z68X-UD3H-B3/Z68X-UD3H-B3
RIP: 0010:[<ffffffff810f73a9>] [<ffffffff810f73a9>]
put_compound_page+0x89/0x170
RSP: 0018:ffff880036887bc8 EFLAGS: 00010286
RAX: ffff8800cdb8ae00 RBX: ffff8800cdb8a800 RCX: ffff8800cdb8b6c0
RDX: 0000000000000140 RSI: 0000000000000001 RDI: ffff8800cdb8a800
RBP: ffff880036887be8 R08: ffff88005ddb4518 R09: 0000000000000010
R10: 0000000000000000 R11: 00007f6f00000000 R12: 0000000000000000
R13: ffffffffa079896c R14: 00000000000091aa R15: ffff880115200900
FS: 0000000000000000(0000) GS:ffff88011fac0000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000000000001c CR3: 000000009f2ff000 CR4: 00000000000427e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process vhost-30506 (pid: 30508, threadinfo ffff880036886000, task
ffff8801088cc020)
Stack:
ffffea00016fbfc0 0000000000000012 ffff880115200900 ffffffffa079896c
ffff880036887bf8 ffffffff810f77ec ffff880036887c18 ffffffff8132046f
ffff880115200900 ffff880115200900 ffff880036887c38 ffffffff8132050e
Call Trace:
[<ffffffff810f77ec>] put_page+0x2c/0x40
[<ffffffff8132046f>] skb_release_data+0x8f/0x110
[<ffffffff8132050e>] __kfree_skb+0x1e/0xa0
[<ffffffff813205c6>] kfree_skb+0x36/0xa0
[<ffffffffa079896c>] tun_get_user+0x71c/0x810 [tun]
[<ffffffffa0798aba>] tun_sendmsg+0x5a/0x80 [tun]
[<ffffffffa07a75d7>] handle_tx+0x287/0x680 [vhost_net]
[<ffffffffa07a7a05>] handle_tx_kick+0x15/0x20 [vhost_net]
[<ffffffffa07a385a>] vhost_worker+0xfa/0x1a0 [vhost_net]
[<ffffffff8105ef80>] kthread+0xc0/0xd0
[<ffffffff8140399c>] ret_from_fork+0x7c/0xb0
Code: 8b 6d f8 c9 c3 48 8b 07 f6 c4 80 75 0d f0 ff 4b 1c 0f 94 c0 84 c0 74 c9
eb bf 4c 8b 67 30 48 8b 07 f6 c4 80 74 e7 4c 39 e7 74 e2 <41> 8b 54 24 1c 49 8d
4c 24 1c 85 d2 74 d4 8d 72 01 89 d0 f0 0f
RIP [<ffffffff810f73a9>] put_compound_page+0x89/0x170
RSP <ffff880036887bc8>
CR2: 000000000000001c
---[ end trace 97d0c820ff95bb21 ]---
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2013-07-05 12:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-05 12:47 bugzilla-daemon [this message]
2013-07-05 15:06 ` [Bug 60518] Heavy network traffic between guest and host triggers kernel oops bugzilla-daemon
2013-07-07 10:19 ` bugzilla-daemon
2013-08-06 8:55 ` bugzilla-daemon
2013-08-07 12:24 ` bugzilla-daemon
2013-08-13 18:57 ` bugzilla-daemon
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=bug-60518-28872@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=kvm@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.