From: Dave Hansen <dave@linux.vnet.ibm.com>
To: Avi Kivity <avi@qumranet.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
kvm-devel <kvm@vger.kernel.org>,
"Anthony N. Liguori [imap]" <aliguori@us.ibm.com>
Subject: Re: KVM overflows the stack
Date: Wed, 16 Jul 2008 23:27:29 -0700 [thread overview]
Message-ID: <1216276049.11664.16.camel@nimitz> (raw)
In-Reply-To: <1216248527.11664.9.camel@nimitz>
A newer gcc (4.2) makes this a wee bit better, but probably still
worrisome.
dave@nimitz:~/src/kvm-userspace-virgin/kernel$ objdump -d *.ko | perl /home/dave/kernels/linux-2.6.git-t61/scripts/checkstack.pl i386
0x00007b33 kvm_arch_vm_ioctl [kvm]: 1164
0x000072e8 kvm_arch_vcpu_ioctl [kvm]: 1060
0x00007497 kvm_arch_vcpu_ioctl [kvm]: 1060
0x0000adad kvm_pv_mmu_op [kvm]: 564
0x0000ae6b kvm_pv_mmu_op [kvm]: 564
0x00002553 kvm_vcpu_ioctl [kvm]: 468
0x0000d7e8 paging64_prefetch_page [kvm]: 304
0x0000d926 paging64_prefetch_page [kvm]: 304
0x0000d936 paging64_prefetch_page [kvm]: 304
0x0000c118 paging32_prefetch_page [kvm]: 300
0x0000c146 paging32_prefetch_page [kvm]: 300
0x0000c286 paging32_prefetch_page [kvm]: 300
0x0000f1eb x86_emulate_insn [kvm]: 192
0x0000f372 x86_emulate_insn [kvm]: 192
0x0000f5f2 x86_emulate_insn [kvm]: 192
0x00005373 kvm_task_switch [kvm]: 172
0x00001466 __kvm_set_memory_region [kvm]: 164
0x000014da __kvm_set_memory_region [kvm]: 164
0x0000dae8 paging64_page_fault [kvm]: 156
0x0000db06 paging64_page_fault [kvm]: 156
0x0000db67 paging64_page_fault [kvm]: 156
0x0000dcd5 paging64_page_fault [kvm]: 156
0x0000dcf1 paging64_page_fault [kvm]: 156
0x0000c356 kvm_mmu_pte_write [kvm]: 152
0x0000c50a kvm_mmu_pte_write [kvm]: 152
0x0000df28 paging32_page_fault [kvm]: 144
0x0000df46 paging32_page_fault [kvm]: 144
0x0000dfa7 paging32_page_fault [kvm]: 144
0x0000e115 paging32_page_fault [kvm]: 144
0x0000e131 paging32_page_fault [kvm]: 144
0x00014ed3 apic_mmio_read [kvm]: 108
-- Dave
next prev parent reply other threads:[~2008-07-17 6:27 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-25 21:12 kvm causing memory corruption? ~2.6.25-rc6 Dave Hansen
2008-03-26 9:50 ` [kvm-devel] " Avi Kivity
2008-03-26 16:52 ` Dave Hansen
2008-03-26 16:58 ` Avi Kivity
2008-03-26 17:16 ` Dave Hansen
2008-03-27 9:36 ` Avi Kivity
2008-03-27 10:10 ` Avi Kivity
2008-03-27 14:55 ` Dave Hansen
2008-03-27 14:59 ` Avi Kivity
2008-03-27 16:30 ` Dave Hansen
2008-06-02 22:30 ` kvm causing memory corruption? now 2.6.26-rc4 Dave Hansen
2008-06-03 0:59 ` Dave Hansen
2008-06-04 13:42 ` Avi Kivity
2008-06-06 7:41 ` Dave Hansen
2008-06-12 13:10 ` Avi Kivity
2008-06-16 18:07 ` Dave Hansen
2008-07-15 18:57 ` kvm causing memory corruption? now 2.6.26-rc8 Dave Hansen
2008-07-16 21:44 ` kvm causing memory corruption? now 2.6.26 Dave Hansen
2008-07-16 22:48 ` KVM overflows the stack Dave Hansen
2008-07-17 5:52 ` Avi Kivity
2008-07-17 6:08 ` Roland Dreier
2008-07-17 14:06 ` Dave Hansen
2008-07-17 14:15 ` Avi Kivity
2008-07-17 6:14 ` Dave Hansen
2008-07-17 6:42 ` Avi Kivity
2008-07-17 6:45 ` [PATCH] update kvm's anon_inodes.c for r/o bind mounts Dave Hansen
2008-07-19 7:33 ` Avi Kivity
2008-07-17 6:27 ` Dave Hansen [this message]
2008-07-17 5:38 ` kvm causing memory corruption? now 2.6.26 Avi Kivity
2008-03-27 15:50 ` [kvm-devel] kvm causing memory corruption? ~2.6.25-rc6 Dave Hansen
2008-03-27 15:53 ` Avi Kivity
2008-03-27 16:30 ` Dave Hansen
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=1216276049.11664.16.camel@nimitz \
--to=dave@linux.vnet.ibm.com \
--cc=aliguori@us.ibm.com \
--cc=avi@qumranet.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox